At leats on macOS it's not possible to scroll the disassembly panel vertically using the scroll bar (there isn't one) or cursor/page keys.
Do people really use the scroll bar nowadays? I mean we invented the scrollwheel.
My main use for a scrollbar is as a visual indicator of how far I am through something.
But to answer your question yes I use a combination of keys, scroll bar and mouse depending on context.
Yep good point, but this requires a refactoring of the Disassembly Widget, so I don't think this will be done for next release.
How far from what? The current section? Map? File? Address space?
On 5 Dec 2017, at 12:12, xarkes notifications@github.com wrote:
Yep good point, but this requires a refactoring of the Disassembly Widget, so I don't think this will be done for next release.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Far from the beginning/end or top/bottom of the disassembly.
"disassembly" does not really mean anything to me. I mean that it's only bytes, and maybe you are talking about the .text section? Which might be interesting but I've seen some binaries executing stuff outside the .text section so it's not very profitable I believe.
"disassembly" as displayed in the user interface

So a scroll bar for about 2**64 lines? Or am I missing something here?
Yes, please enable the vertical scroll bar to use as a visual gauge of position.
and ability to move through disassembly using cursors or page buttons.
Horizontal scroll bar is already enabled.
cc @thestr4ng3r
Cursor and page keys are straight-forward and absolutely useful. I will probably implement those soon.
About the scrollbar, I see the same problem as @xarkes. We could say the range of the scrollbar is the complete memory range mapped to the file or the current section.
Take a look at Hopper for example. It has a scrollbar that goes through all mapped memory. But as soon as you have a file of a certain size, moving the scrollbar by a single pixel makes disassembly jump all over the place, so the scrollbar is no more useful except as a visual indicator for where you roughly are.
However, if the desired use of the scrollbar is a only as a visual position indicator, I would rather add that to the GraphicsBar that is currently displayed below the toolbar to show the position of the current seek, like Hopper does with this small red arrow for example:

I will maybe experiment with a scrollbar at some point, but I totally agree with @xarkes and @radare. It is less useful than you might initially think.
That works for me. Thanks for your understanding.
Also reminds me of Sublime mini map

Most helpful comment
Cursor and page keys are straight-forward and absolutely useful. I will probably implement those soon.
About the scrollbar, I see the same problem as @xarkes. We could say the range of the scrollbar is the complete memory range mapped to the file or the current section.

Take a look at Hopper for example. It has a scrollbar that goes through all mapped memory. But as soon as you have a file of a certain size, moving the scrollbar by a single pixel makes disassembly jump all over the place, so the scrollbar is no more useful except as a visual indicator for where you roughly are.
However, if the desired use of the scrollbar is a only as a visual position indicator, I would rather add that to the GraphicsBar that is currently displayed below the toolbar to show the position of the current seek, like Hopper does with this small red arrow for example:
I will maybe experiment with a scrollbar at some point, but I totally agree with @xarkes and @radare. It is less useful than you might initially think.