search

RupertAvery / et3400-emu

A Heathkit ET-3400 Emulator written in C#
BSD 2-Clause "Simplified" License
12 stars 9 forks source link

Allow line-by-line mouse wheel scrolling of Disassembly and Memory panes #2

Open RupertAvery opened 5 years ago

RupertAvery commented 5 years ago

Load fsr1.obj and DO 0000 so it runs.
View Debugger.
Load fsr1.map. Disassemble RAM (see 0000-000F instructions, 0011 "DATA", good).

Then I tried to scroll the Disassembly window by rolling my mouse wheel.

It scrolls the Disassembly choice (since it is still selected) and jumps the Disassembly pane unexpectedly.

I would like to be able to scroll the Disassembly pane (and Memory too?) line-by-line using the mouse wheel.

RupertAvery commented 5 years ago

Scrolling the Disassmbly and Memory panes using the mouse wheel should work.

I tried to replicate the behavior but it seems to run fine for me. I'm using a touchpad to scroll but it should have the same behavior as a mouse wheel.

mouse-wheel-scroll

The cursor should be over the pane you wish to scroll.

ricknun commented 5 years ago

Version 1.0.7 Beta 2 update: (Very cool video above!) Doing the same operations you show, I do not get the desired behavior using my mouse wheel. Nothing changes in the Memory or Disassembly windows as I roll the wheel. I tried both hovering over each pane, and clicking in them first, but no response to the wheel. (I think the only way I can change the disassembly address in this release is to page to it using the scroll bar area to the right of the pane.)

Update later in the day: If another application such as my text editor is the active window then hovering the mouse over the Memory or Disassembly panels and rolling the mouse wheel scrolls their display. If either the emulator or debugger windows are the active window, nothing happens. But even when it scrolls the scrolling is not as expected -- I would expect a single click of the wheel away from me to scroll the window contents down, the same as a text editor, so I can see lower-numbered addresses. It does the opposite. Also I would expect it to scroll one line per mouse-wheel click. It instead it scrolls a page (minus 2 lines that are repeated) per mouse-wheel click.