Community
Participate
Working Groups
Traditional Memory Rendering defines the scroll range to cover the whole addressable memory range which for a standard 32bit architecture would mean with a single mouse drag to move memory view to display any of 2.147.483.647 lines of scroll. With this amount of total lines to scroll, scrollbar slider is not quite usable for positioning memory view to desired location (or even close to it), as any minor mouse movement will move the visible address by tenths of megabytes. I propose to address this in a similar way as platform hex rendering does for dynamic loading mode. i.e. an workspace preference to specify number of lines for scrolling. IMHO, a default ~100 lines is quite reasonable. Once user scrolls close to top/bottom the scroll area will be re-positioned.
The issue is a follow-up on Bug 387500