Anyone using GLX2???

Jerry Daniels jerry at
Thu Mar 6 10:53:13 EST 2008


We use the command "breakpoint" in the code to indicate a breakpoint  
in GLX2. This has solved many other problems in the  
constantly migrating red dots and performance problems on large  
scripts in the Rev script editor.

Once in the GLX2 debugger, you can easily set additional breakpoints  
by clicking on any link whereupon it will become bold and stop the  
debugger when encountered.

There is significant documentation on our support site and on our web  
site indicated below. There is a support site, but you have to sign up  
for it. We didn't get any request for support sign-up from you, but I  
will check into this and make sure you're on board.

Sorry for your frustrations, but we can get it all sorted out for you.


Jerry Daniels

Daniels & Mara, Inc.
Makers of GLX2

On Mar 6, 2008, at 8:33 AM, Dave wrote:

> Hi,
> Has anyone used GLX2? I started using it a couple of days ago and  
> have had nothing but problems on the debugging side and with no  
> decent documentation I can find and no support it's hard to know how  
> it is *supposed* to work rather than what I am seeing.
> 1.  I can find no way to insert or remove a breakpoint without  
> aborting the current debugging session. The "Breakpoint" menu item  
> just inserts a "breakpoint" statement into the source code. It says  
> clicking on it will disable/enable it, but this doesn't seem to have  
> any effect, it always breaks regardless of if it's highlighted or  
> not. The only way I can find to remove the breakpoint is to edit the  
> source code and physically delete the "breakpoint" statement, which  
> kill the current session.
> 2. Old breakpoints added with the standard RunRev IDE Script Editor  
> (the red dot at the left of the statement) triggers the GLX2  
> Debugger and I can find no way to get rid of them. The amusing thing  
> here is that the standard debugger ignores them, so you can't tell  
> where they are until GLX2 finds them and GLX2 can't remove them!
> 3. The editor or debugger seems to lose track of which is the latest  
> version of the Script and so the code that is run is not the same as  
> the code displayed in the Source Window.
> I've sent two emails a week apart asking to be registered for  
> support but no reply.
> These issues are making it unusable and I'm about to uninstall it,  
> which is a real shame since the editor is miles better than the  
> standard IDE version.
> All the Best
> Dave
> _______________________________________________
> use-revolution mailing list
> use-revolution at
> Please visit this url to subscribe, unsubscribe and manage your  
> subscription preferences:

More information about the Use-livecode mailing list