Ted,
For 160095, I think we should indicate the
viewport position within the start/end bounds of the memory. The current design
always leads me to think that I can still scroll up or down even though I am
already in top/bottom bound.
For 158553, scrolling to the hard top or
bottom should cause a scroll to the start/end bounds of memory. With the
current design, there is no easy way for me to scroll to the top bound or
bottom bound. I had to use the Go To Address to accomplish this. This forfeits the
purpose of dragging the thumb nail.
From: Williams, Ted
[mailto:ted.williams@xxxxxxxxxxxxx]
Sent: Friday, October 06, 2006
8:43 PM
To: Lee,
Alain; Device Debugging developer discussions
Cc: Swiezawski,
Martin
Subject: RE: Traditional Memory
Window
Alain,
What ideas do you have for
fixing 160095? Using the thumb to indicate viewport position within a
large memory block tends to make the thumb size unusually small. Do you have an
alternative design in mind?
For 158553, should moving the thumb to the
hard top or bottom cause a scroll to the start/end bounds of memory?
Or should the entire range of thumb movement within the page increment
area represent only a subset of the available memory range?
ted
From: Lee, Alain [mailto:a-lee@xxxxxx]
Sent: Friday, October 06, 2006
2:38 PM
To: Williams, Ted
Cc: Swiezawski,
Martin
Subject: RE: Traditional Memory
Window
Ted,
I am currently working on the fixes for
these bugs:
158553
|
nor
|
P3
|
PC
|
NEW
|
|
vertical scroll bar thumb control does
not scroll the window
|
158596
|
nor
|
P3
|
PC
|
NEW
|
|
Address column in memory window is
partially displayed
|
160095
|
nor
|
P3
|
PC
|
NEW
|
|
Thumb selection is always at the
middle of the scroll bar
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|