On 1/25/12 1:40 PM, Bob Sneidar wrote:
That may help whoever at RR to troubleshoot it. If
I knew where in the library this was handled I would troubleshoot it
myself!
They won't see it here, it needs to go into the QCC.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperAct
In the default debugger you can select the Breakpoints in the lower tab. Then
right-click and select New Watch. Select Global Scope in the Handler popup.
Select a global variable in the Variable popup. Set a condition (or no it
doesn't matter). Click OK. Crash to desktop. DISCLAIMER: Save your c
On 1/24/12 11:28 PM, Mark Wieder wrote:
You're confusing breakpoints and watched variables. It used to be that you
couldn't set a watch on a global variable, but that bug (6506) was fixed in
version 4.5.2. If you're using PowerDebug for this, just click to the left of
the global name in the glob
Ok I see. When I first clicked next to the variable it was not a global so
that is why when I declared it to a global later it didn't CTD. I went back and
checked the watch point and it's scope was the script of the stack. When I set
it's scope to global, LC immediately crashes. Sorry for the c
Well darned it I just went back and tried again, making the variable a global
and it did NOT crash to desktop!! How odd!
Bob
On Jan 24, 2012, at 9:28 PM, Mark Wieder wrote:
> Bob Sneidar writes:
>
>> though. This is a feature that used to work. I know because GLX2 used to do
> this successf
Oddly, watchedVariables is not in the dictionary. I created a new stack, set a
global in the stack script, created an Openstack handler, set a breakpoint in
the first line of the handler, and changed the value of the global twice, once
to empty and once to a string of text. I ran OpenStack and w
Hi Mark. Actually, this was back when GLX2 encompassed the debugger too.
Apparently you still cannot set a watched variable on a global. That is the
problem I am having. The instant I set the watched variable I crash to desktop.
It may be an issue with watching an array variable. I will check th
Thanks Mark - I didn't know about the watchedvariables.
Phil
On 1/24/12 9:28 PM, Mark Wieder wrote:
Bob Sneidar writes:
though. This is a feature that used to work. I know because GLX2 used to do
this successfully.
You're confusing breakpoints and watched variables. It used to be that you
Bob Sneidar writes:
> though. This is a feature that used to work. I know because GLX2 used to do
this successfully.
You're confusing breakpoints and watched variables. It used to be that you
couldn't set a watch on a global variable, but that bug (6506) was fixed in
version 4.5.2. If you're us
Okay I found another obscure instance of the same thing and fixed it. I have
learned a valuable lesson: Bail from handlers when there is no point
proceeding. An empty value for the dhHilitedIndex in this particular handler
produced the same visible results, but ended up setting my array (which t
yup found one instance of that. Have to be careful though because I have a
second datagrid that is populated with related table data and uses the values
in the array in it's own query. I just have to pore through the code.
Bob
On Jan 24, 2012, at 1:22 PM, Phil Davis wrote:
> Hmmm. You proba
Hmmm. You probably already tried this, but... can you check for a non-empty
value in dgHilitedIndex before allowing the 'put... into...' to proceed? Of
course that's still a problem if it happens in 14 dozen different places.
Maybe put the actual setting of the array inside a setProp handler, s
Aye I can already do that as a scripted breakpoint. if myGlobal is not an
array. But where to put it? By the time it comes back from something I call a
single key has been created by another handler, and there is no line I have
encountered so far that actually sets it to empty. What is actually
I see. After reading Jacque's contribution also, maybe you want something like
this in your script?
if the keys of gMyGlobal = empty then breakpoint
Phil
On 1/24/12 9:30 AM, Bob Sneidar wrote:
Hi Phil. I cannot change the variable to a local because it is the array that
contains the rec
Hi Phil. I cannot change the variable to a local because it is the array that
contains the record data for the form I am using, so all objects have to be
aware of it.
You set a variable checkpoint either in the debugger, or by script. I'll be
daggum if I remember the script command though.
B
No, I mean I want to break when the value of the variable is something. In the
default script editor there is a tab called Breakpoints. You can set something
called a watch. You can set the scope to be global, and enter a variable, and
set the break to happen when the variable matches a conditio
On 1/23/12 4:30 PM, Bob Sneidar wrote:
I've mentioned it before, that if you set a breakpoint on a global,
the IDE will crash to desktop.
If you mean trying to break on a global declaration, I'm not sure how
that could work at all. That's just a memory assignment. There's nothing
to break on,
Hi Bob,
Does it crash when you set a breakpoint on a local? If not, can you change the
global to a local variable?
Just grasping at straws... I've never set a breakpoint on a variable
declaration. Didn't know you could. Is your global declared in a handler or
outside all handlers? (I assume
I've mentioned it before, that if you set a breakpoint on a global, the IDE
will crash to desktop. I have verified this is a problem even when all plugins
are disabled. Does anyone know a workaround for this? I am in desperate need of
finding where an array is getting set to empty. For whatever
19 matches
Mail list logo
