Latest version of Glider debugger does not function

So I set a breakpoint as one of the first lines in main.lua and then click the icon with the 1-2-3 on it (Debugger). It was working last I remember, but now, no debugger. Nothing.

Working with LuaGlider used to be such a delight.  But now, with the constant freezes and losing breakpoints its rapidly approaching “more trouble than its worth,” which is sad, because it used to be a great (and STABLE) IDE.

To “fix” skipping breakpoints, you need to shut down LuaGlider, and then shut down all the other instances that have a nasty habit of appearing (if you keep using LuaGlider, the Task Manager window will rapidly earn a place of prominence in your workflow).

Yes, LuaGlider was excellent for a year or so - but the fact that it does not report errors is unforgivable and the reason I ultimately had to leave it. I’m now using ZeroBraneStudio and would recommend any advice regarding something better. I’d like something as simple as displaying errors in a different color than my print output.

I just recently (this week) switched from Glider to ZeroBrane and love it.

We are looking to switch as well, Glider seems to be too unstable on Windows, and cannot use any other Java version other than the included 1.6, (Others will make it crash on startup) which i think is the cause of most problems. It’s been working Ok for me on Mac with Java 1.7, though.

Only downside to ZeroBrane right now is it’s configuration is not so user friendly, but… it is open source, which is great!

> I’d like something as simple as displaying errors in a different color than my print output.

@troylyndon, this should be doable; I’ll take a look at how this can be added.

Working with LuaGlider used to be such a delight.  But now, with the constant freezes and losing breakpoints its rapidly approaching “more trouble than its worth,” which is sad, because it used to be a great (and STABLE) IDE.

To “fix” skipping breakpoints, you need to shut down LuaGlider, and then shut down all the other instances that have a nasty habit of appearing (if you keep using LuaGlider, the Task Manager window will rapidly earn a place of prominence in your workflow).

Yes, LuaGlider was excellent for a year or so - but the fact that it does not report errors is unforgivable and the reason I ultimately had to leave it. I’m now using ZeroBraneStudio and would recommend any advice regarding something better. I’d like something as simple as displaying errors in a different color than my print output.

I just recently (this week) switched from Glider to ZeroBrane and love it.

We are looking to switch as well, Glider seems to be too unstable on Windows, and cannot use any other Java version other than the included 1.6, (Others will make it crash on startup) which i think is the cause of most problems. It’s been working Ok for me on Mac with Java 1.7, though.

Only downside to ZeroBrane right now is it’s configuration is not so user friendly, but… it is open source, which is great!

> I’d like something as simple as displaying errors in a different color than my print output.

@troylyndon, this should be doable; I’ll take a look at how this can be added.