Do you ever miss the cool breakpoint features other IDEs have?
Would debugging be SO much easier if you could step line-by-line through your code?
Look no further! You can sort of simulate that behavior mostly kind of with Breakpoint!
Attached is a copy of the builtin “Flappy” project that demonstrates the two breakpoint modes offered; a straight-up normal breakpoint, that stops the code wherever it’s placed and then lets you jump back into the action, and a step-by-step breakpoint where you can examine what’s going on with a fine-toothed comb.
I’ve posted some code that used this method before, but this is the first time I’ve made it general enough to be used by anyone for any purpose. It’s far from perfect, and has some severe limitations, but it’s pretty good, and personally, it helped me find my way through some absolutely maddening bugs I had previously spent days tracking down.
…but don’t use it! Or maybe do! Just be careful!..
Like with TabInator, there’s currently a Codea bug that this can trigger (a different one) . This one doesn’t lose your data, so it’s not as much of a “maybe just don’t use this at all right now” situation. It is super annoying though, because it makes the play button stop working, and you have to close Codea completely and re-open it before the play button works again.
And that said, again I personally have found this extremely helpful even with that bug un-solved. There was just no other way to get at the guts of my code while it was running, and I was willing to live with the drawbacks to untangle the mess I was in.
So yeah. I think this is cool too. Just be aware that, currently, it comes with some drawbacks.
…also it should be noted that, in the end, this is a pretty shoddy stand-in for actual debugging tools. Codea still really needs that, and this stopgap jalopy doesn’t come close to fitting that bill.