-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow the debugger to change register values #247
Comments
Having the option to edit the registers is definitely a good idea and I was planning to support it (hence the editable field) but then forgot about it ! One concern I have is the risk of changing the values by mistake. An option could be to have a confirmation button. On the other hand, having to click an extra button can be a pain... This option is fine so far IMO. More problematic is the fact that the value is displayed in 3 fields (hex, dec and char) but only one is read when resuming the execution. An easy fix is to have only the hex field editable and make the others read-only. Alternatively (I don't remember how hard it would be to do), updating one field would directly update the others. Note to self: I double checked and changing So in a nutshell, please do proceed with a PR. If you can make the dec & char fields read-only or ensure updating one of the 3 fields update the other 2 it would be nice. Thanks! |
Added a basic support for editing registers. This only support editing the hexadecimal values, and for registers that are displayed both as 1 bit and/or 8 bits and/or 16 bits, only one of the two versions (e.g. H not HL, F not individual flags, etc...) More work would be needed to make things better, but this should already be quite useful. |
I'm working on the reimplementation of some CPC games for ScummVM and I needed some debugging to change registers during the execution. Caprice32 allows to see the registers in the developer's tool and the fields are editable, but changing them will not do anything, so I did a quick patch:
If you think this approach looks good, I can complete this code and create a small PR. Otherwise, this is a small feature request to make the debugger more useful.
The text was updated successfully, but these errors were encountered: