Pedro de Medeiros

I think this issue can be considered closed now, right?

I have an idea to fix this, but to be thorough it has to be a three part fix: 1) connect DebuggerForm::connected to DisasmViewer::refresh to force the debugger to fetch...

> Point 2 can indeed be a problem. Setting a large watchpoint on the full 64k range will indeed trigger the slow-emulation-path on all memory accesses. That's not ideal. Depending...

This issue is about the code view widget and how you can't easily change the address boundary where an instruction starts and where it ends. Let's say you have the...

This is actually pertaining to this OpenMSX [issue](https://github.com/openMSX/openMSX/issues/1550) but I will take a look.

> Is your app properly respecting the io.WantCaptureKeyboard flag ? Yes, it is. Is there a way to tell if a ImGui widget used the key event it received? If...

> Can you clarify what "game/app" stands for, what it is doing to access keys? (call order, API, tests performed etc) OpenMSX uses Dear ImGui to display its debugger, but...

What about the case when we know exactly the slot, subslot and segment of a label? Besides, NOI files store addresses only, not constants like the `delay` you defined above....

I find it annoying that labels can be completely ignored if they are not aligned with instructions addresses, specially if they are on the right slot and segment. Can't we...

> What do you propose? Split anyway (under what conditions exactly?) Or show some other visual indicator? If so, then what/how? I propose visual cues when there is a label...