@M.Y.
Debugger & editor observations on a Mac.
I found, if I don’t use the Stop Debug button between code changes, debug appears to work properly. I can add new lines, set breaks before or after the save (and after relaunch), then RELAUNCH the Sim (which comes up automatically after saving), and debugging works as expected. I thought I would have to stop/restart debugger for code changes to be seen. As a a scripting language, is this not necessary?
And if I see the OS color wheel spinning when the cursor is over the Sim, that just means I need to press play on the debugger to start execution again.
This method makes for really fast iterations, even with debug. It also doesn’t liter the launch bar with Sim icons either.
EDIT: This is crazy cool. I just confirmed what I wrote above to be true. I am jumping around changing things in different files, adding lines, breaks, saving changes and relaunching. If I need a break just click a line while things are running, and when it hits, it pauses right there. View variables, step, make changes and click play.
And if I get engrossed in the simulator, testing the app, and I see the color wheel spinning, I find that I have hit a break point when I glance back over to the Cider Debugger. If I no longer want it, click to remove and hit play. Awesome!!!
Your error indicator at the line number has been helpful also, it catches typos. Nice work M.Y. [import]uid: 47723 topic_id: 23072 reply_id: 93587[/import]