| Reporter |
Joe White (joewhite)
|
|---|---|
| Created | Jan 8, 2010 10:06:37 PM |
| Updated | Apr 9, 2018 4:00:24 PM |
| Resolved | Apr 9, 2018 4:00:24 PM |
| Subsystem | No Subsystem |
| Assignee | Ilya Ryzhenkov (orangy) |
| Priority | Normal |
| State | Obsolete |
| Type | Usability Problem |
| Fix version | No Fix versions |
| Affected versions | No Affected versions |
| Fixed In Version ReSharper | Undefined |
| VsVersion | All Versions |
Using ReSharper 5 beta (5.0.1565.10):
Open Find Usages, for something big enough to have a vertical scrollbar. Put the mouse pointer over the "down-arrow" button on the scrollbar. Press and hold the left mouse button.
Expected: the list should scroll one line, pause briefly (around a quarter of a second), then start scrolling continuously. I.e., the scrollbar should act like a scrollbar.
Actual: the list scrolls one line, then stops. To keep scrolling, I have to click repeatedly.
This doesn't always occur. It seems to be related to the strange state described in RSRP-146356: when ReSharper gets into the state where it insists on putting all of its menus and tooltips in the top-left corner of the primary monitor, then scroll repeat breaks too. Are the screwed-up screen coordinates being used for hit testing, perhaps?
Open Find Usages, for something big enough to have a vertical scrollbar. Put the mouse pointer over the "down-arrow" button on the scrollbar. Press and hold the left mouse button.
Expected: the list should scroll one line, pause briefly (around a quarter of a second), then start scrolling continuously. I.e., the scrollbar should act like a scrollbar.
Actual: the list scrolls one line, then stops. To keep scrolling, I have to click repeatedly.
This doesn't always occur. It seems to be related to the strange state described in RSRP-146356: when ReSharper gets into the state where it insists on putting all of its menus and tooltips in the top-left corner of the primary monitor, then scroll repeat breaks too. Are the screwed-up screen coordinates being used for hit testing, perhaps?