Based on the earlier discussion, I've added on/off methods to the debugger to wrap a fragment you want to debug (and turn debugging off for the rest of the code). I've tested it on something complex (like zoetrope and a couple of games) and the performance is the same as with running without the deb...

Congratulations! :awesome: While admittedly I also can't imagine using anything other than Vim for now (until Light Table is released), I would guess that debugging support will be useful for a lot of people. Live coding could also be a compelling use case. Do the number sliders work with LÖVE? LIC...

Not necessarily the case, if you can find which function you're in, you can do line hooks for just that function. I thought so too, but it proved to be challenging (if at all possible). Either the line hook is already installed (then it will have most or all of the processing it currently has) or i...

it would also be nice to be able to take the "jump to function" drop down and optionally sort it alphabetically. The current order has an advantage of showing the structure of the file "at a glance" and also of putting "local" functions relative to other functions wher...

It might be interesting to see if a dynamic step size could be implemented, i.e. set it to go 100 lines by default, but if it sees that there's a breakpoint coming up in 30, temporarily set it to less, so you can get there. Now, with calls and all this would be incredibly hard to get right, but eve...

Hi Lap, There is no question Decoda is going to be faster as it works directly with the Lua state, whereas ZeroBrane Studio (or, more specifically, MobDebug) is using debug hooks, so it's called on every line. Using this method though gives it some advantages over Decoda (although speed is not one o...

Thanks Robin; found it in the repo: https://bitbucket.org/rude/love/src/3cb ... s/boot.lua. For some reason it wasn't in the source archive.

bartbes wrote:It's not possible at the moment, it is however a small code change if you can/want to use a modified version of love.

Any plans to implement this? I prefer to use the standard version of love. Just in case, where would I make the change? boot.lua.h?

Type guessing was mentioned in the features list. By trapping errors, I mean allowing the user to examine the state of the program, in the stack view, after an error has occurred. For the type guessing I think we meant the logic in this fragment (https://github.com/pkulchenko/ZeroBraneStudio/blob/m...

bartbes wrote:However, there is no jit module/variable, since it's running on lua, not luajit.

Right, but it is a general debugger that has specific handling for applications that run on luaJIT. I changed the check, so the message should only appear once per session.