Is there a reason that the Properties Viewer only auto-updates non-PPU panels once per second? This is almost useless for following the S-DSP registers of music notes which change many times a second. IIRC it was also almost useless for following S-SMP timers which were in constant motion, and I actually found a mouse auto-clicker program to spam Refresh to increase the refresh rate.
In my local copy of the program, I added a hack to reload the panels every 5 frames (10 Hz on PAL, 12 Hz on NTSC). Perhaps all panels could be reloaded at full frame rate, but I'm not sure if some users are relying on being able to read the text on each refresh. Or (more difficult) they could be reloaded at a user-configurable rate instead (though this may be tricky... should reloading be kept in sync with QTimer's timing source, or the emulator core? If you use frames as a timing source, do you convert Hz to frames?).
Is there a reason that the Properties Viewer only auto-updates non-PPU panels once per second? This is almost useless for following the S-DSP registers of music notes which change many times a second. IIRC it was also almost useless for following S-SMP timers which were in constant motion, and I actually found a mouse auto-clicker program to spam Refresh to increase the refresh rate.
In my local copy of the program, I added a hack to reload the panels every 5 frames (10 Hz on PAL, 12 Hz on NTSC). Perhaps all panels could be reloaded at full frame rate, but I'm not sure if some users are relying on being able to read the text on each refresh. Or (more difficult) they could be reloaded at a user-configurable rate instead (though this may be tricky... should reloading be kept in sync with QTimer's timing source, or the emulator core? If you use frames as a timing source, do you convert Hz to frames?).