Bug 469961 - Traditional Memory Rendering should allow to narrow scrollable area for an easier positioning using scrollbar slider
Summary: Traditional Memory Rendering should allow to narrow scrollable area for an ea...
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-memory (show other bugs)
Version: 8.6.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on: 387500
Blocks:
  Show dependency tree
 
Reported: 2015-06-11 11:08 EDT by Teodor Madan CLA
Modified: 2020-09-04 15:19 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Teodor Madan CLA 2015-06-11 11:08:26 EDT
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.
Comment 1 Teodor Madan CLA 2015-06-11 11:09:25 EDT
The issue is a follow-up on Bug 387500