Nice! No more revLibUrl cloning for me.
Phil
On 12/10/15 3:08 AM, Ali Lloyd wrote:
Hi Dan,
The global gRevDevelopment controls whether breakpoints trigger in scripts
in stacks with rev-prefixed names.
If you do
put true into gRevDevelopment
in the message box, the breakpoints should trigger.
A
It can also be changed in the variable pane of the message box if you want a UI
for it.
On December 10, 2015 10:46:07 AM CST, Mark Wieder
wrote:
>On 12/10/2015 03:08 AM, Ali Lloyd wrote:
>> Hi Dan,
>> The global gRevDevelopment controls whether breakpoints trigger in
>scripts
>> in stacks with
On 12/10/2015 03:08 AM, Ali Lloyd wrote:
Hi Dan,
The global gRevDevelopment controls whether breakpoints trigger in scripts
in stacks with rev-prefixed names.
If you do
put true into gRevDevelopment
in the message box, the breakpoints should trigger.
And just to be clear, in the messagebox type
Hi Dan,
The global gRevDevelopment controls whether breakpoints trigger in scripts
in stacks with rev-prefixed names.
If you do
put true into gRevDevelopment
in the message box, the breakpoints should trigger.
Ali
On Thu, Dec 10, 2015 at 3:06 AM Phil Davis wrote:
> Hi Dan,
>
> In 6.7 I was able
Hi Dan,
In 6.7 I was able to clone the revLibUrl button or stack (I forget which
is used in 6.7.x), rename it, stop using (or remove from front, or ...)
the actual rev one and start using my copy. Then the debugger would go
into the revLibUrl code like I wanted, so I could see what was happeni
