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
Dave wrote:
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
Have you considered contacting the vendor?
While I haven't seen documentation that completely
Dave,
We use the command breakpoint in the code to indicate a breakpoint
in GLX2. This has solved many other problems in the process...like
constantly migrating red dots and performance problems on large
scripts in the Rev script editor.
Once in the GLX2 debugger, you can easily set
On 6 Mar 2008, at 15:23, Richard Gaskin wrote:
Dave wrote:
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
Have you considered contacting the vendor?
While
Dave,
I have just responded on the list here. As far as putting on the GLX2
support site, sometimes our emails end up in the spam folder. You
might check there,
Best,
Jerry Daniels
Daniels Mara, Inc.
Makers of GLX2
http://www.daniels-mara.com/glx2
On Mar 6, 2008, at 9:55 AM, Dave
Hi,
Checked the Spam folder, nothing in there from your domain. Here is a
copy of the emails I sent:
From: [EMAIL PROTECTED]
Subject:Support Request
To: [EMAIL PROTECTED]
Hi,
Could I register for support? My license key is:
First name: Danny
Last name: Shisler
Unlock
Hi,
We use the command breakpoint in the code to indicate a
breakpoint in GLX2. This has solved many other problems in the
process...like constantly migrating red dots and performance
problems on large scripts in the Rev script editor.
It may have fixed bugs in the RunRev Script Editor,
On Mar 6, 2008, at 12:01 PM, Dave wrote:
t may have fixed bugs in the RunRev Script Editor, but wouldn't it
have been better to fix the problem instead of having two parallel
ways of setting a breakpoint, especially since the way in which the
Standard Script Editor works is in line with
My name is Malte and I am a GLX2 user. Currently I am undergoing a 12
step program to be able to live without it at customers places...
Jokes aside:
Never ever will I want to switch back to the original Script Editor in
the IDE. Working with GLX is such a relief, once you get used to it.
And I'll second the endorsement - it's a great product and an
essential part of my workflow, from a company that listens to its
customers. (Thanks for Tahoma, Jerry!)
I'll never go back to tens of script windows open at the same time...
My name is Malte and I am a GLX2 user. Currently I am
You're welcome, Stephen!
Best,
Jerry Daniels
Daniels Mara, Inc.
Makers of GLX2
http://www.daniels-mara.com/glx2
On Mar 6, 2008, at 3:18 PM, Stephen Barncard wrote:
And I'll second the endorsement - it's a great product and an
essential part of my workflow, from a company that listens to
First off, I haven't seen any mention of which version of GLX2 you are
running. I experienced similar problems as you described with an earlier
version of GLX2, but as soon as I updated they were all solved. I now go
beyond the release and use the latest Beta version.
Depending on how old your
12 matches
Mail list logo
