> Hmm, I had to missed something, it seems. How does it work exactly? > Does anybody has a complete up-to-date documentation on monitor, especially > new features, etc? I'm not sure what you're asking. How does what work exactly? > Btw, is stepping really slow with memory update? I mean, stepping is for > tracing a program for humans, I can't see too much point to do more quickier > than eg max of 0.1sec/step. Or is it even slower? And as far as I see the Yes it's slower than 0.1sec/step. Slow enough, anyway, that I didn't like its responsiveness and would probably not use my own tool based on that! > problem you may need to update only the memory part which is shown for the > user actually, if memory window is "scrolled" etc, then other parts can be > transferred on-demand. These optimizations are possible, yes. I wanted to get the major framework done first, and that is what this release is. The optimizations will require quite a bit of internal rework as the NES emulator in NESICIDE is completely visible to the running program internally, so its responsiveness is quite fast. I provided this release in hopes that someone might try it and provide feedback. Any feedback is helpful! Christopher ---------------------------------------------------------------------- To unsubscribe from the list send mail to majordomo@musoftware.de with the string "unsubscribe cc65" in the body(!) of the mail.Received on Fri Apr 13 19:44:16 2012
This archive was generated by hypermail 2.1.8 : 2012-04-13 19:44:19 CEST