Re: breakpoints being ignored

[Sannyasin Brahmanathaswami via use-livecode]

Mike Kerner :

Bingo.  It happens in 9 when using the remote debugger.  The Script
Debugging gets disabled during this process.

ditto what Mike said, confirmed again here today…"gotcha", because the check 
mark remains on the IDE menu and toggling the menu item on and off doesn't seem 
to help.

BR

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Mike Kerner via use-livecode]

Bingo.  It happens in 9 when using the remote debugger.  The Script
Debugging gets disabled during this process.

On Thu, Mar 9, 2017 at 11:45 AM, Dr. Hawkins via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On Thu, Mar 9, 2017 at 7:43 AM, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > I need to see if I can make it happen, again.  I wonder if going back and
> > forth between 9 to do remote debugging and 8 because 9 has issues may be
> > causing it.  Will file a bug report if I can repeat it.
> >
>
> FWIW . . . when early 7 got too bad, I'd load and save again in 5, reload
> in 7, and things usually got a bit better.
>
>
>
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Dr. Hawkins via use-livecode]

On Thu, Mar 9, 2017 at 7:43 AM, Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I need to see if I can make it happen, again.  I wonder if going back and
> forth between 9 to do remote debugging and 8 because 9 has issues may be
> causing it.  Will file a bug report if I can repeat it.
>

FWIW . . . when early 7 got too bad, I'd load and save again in 5, reload
in 7, and things usually got a bit better.



-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Mike Kerner via use-livecode]

I need to see if I can make it happen, again.  I wonder if going back and
forth between 9 to do remote debugging and 8 because 9 has issues may be
causing it.  Will file a bug report if I can repeat it.

On Thu, Mar 9, 2017 at 5:58 AM, Ali Lloyd via use-livecode <
use-livecode@lists.runrev.com> wrote:

> These issues sound like they are to do with Script Debug Mode. Please check
> if this is turned on in the Development menu.
>
> Mike, this sounds like it was probably your issue too, especially if
> trashing your prefs fixed it, as Script Debug Mode on is the default.
>
> It *does* sound like there may be a new issue with Script Debug Mode
> getting turned off somehow, which seems worth looking into.
>
> On Thu, Mar 9, 2017 at 6:29 AM Sannyasin Brahmanathaswami via use-livecode
> <
> use-livecode@lists.runrev.com> wrote:
>
> > Interesting… this was happening to me today. on a hunch I set the
> > gRevDevelopment to true… thinking that because I had messed with that
> > yesterday while using the remote debugger on my android phone… I had done
> > something that was blocking script debug --  related to the action of
> > answering "No" to the dialog asking if you want to run a remoteDebug
> > session,  just after installing the standalone on the phone… because I
> > thought (have yet to test/reproduce… very tedious…) possibly that is at
> > least one action that might toggle script debug mode to off (even though
> it
> > appears checked?) and so your break point could possibly be ignored at
> that
> > point and until you reboot LC?
> >
> > Dunno, just was just fishing for possible recipes…
> >
> > but aha, gRevDevelopment, true:  the break point was "honored" Of course
> > it starting stepping through a lot of IDE code, so I had to go back and
> set
> > the gRevDevelopment to "false"  and now the break points work…
> >
> > ….of course if it goes all the way back to 8.1.3 and 6, then it could be
> > anything….
> >
> > BR
> >
> >
> > Mike Kerner wrote:
> >
> > Add a "breakpoint" line as the first line in the script
> > execute again
> > breakpoint still doesn't fire.
> >
> > ___
> > use-livecode mailing list
> > use-livecode@lists.runrev.com
> > Please visit this url to subscribe, unsubscribe and manage your
> > subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Ali Lloyd via use-livecode]

These issues sound like they are to do with Script Debug Mode. Please check
if this is turned on in the Development menu.

Mike, this sounds like it was probably your issue too, especially if
trashing your prefs fixed it, as Script Debug Mode on is the default.

It *does* sound like there may be a new issue with Script Debug Mode
getting turned off somehow, which seems worth looking into.

On Thu, Mar 9, 2017 at 6:29 AM Sannyasin Brahmanathaswami via use-livecode <
use-livecode@lists.runrev.com> wrote:

> Interesting… this was happening to me today. on a hunch I set the
> gRevDevelopment to true… thinking that because I had messed with that
> yesterday while using the remote debugger on my android phone… I had done
> something that was blocking script debug --  related to the action of
> answering "No" to the dialog asking if you want to run a remoteDebug
> session,  just after installing the standalone on the phone… because I
> thought (have yet to test/reproduce… very tedious…) possibly that is at
> least one action that might toggle script debug mode to off (even though it
> appears checked?) and so your break point could possibly be ignored at that
> point and until you reboot LC?
>
> Dunno, just was just fishing for possible recipes…
>
> but aha, gRevDevelopment, true:  the break point was "honored" Of course
> it starting stepping through a lot of IDE code, so I had to go back and set
> the gRevDevelopment to "false"  and now the break points work…
>
> ….of course if it goes all the way back to 8.1.3 and 6, then it could be
> anything….
>
> BR
>
>
> Mike Kerner wrote:
>
> Add a "breakpoint" line as the first line in the script
> execute again
> breakpoint still doesn't fire.
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Sannyasin Brahmanathaswami via use-livecode]

Interesting… this was happening to me today. on a hunch I set the 
gRevDevelopment to true… thinking that because I had messed with that yesterday 
while using the remote debugger on my android phone… I had done something that 
was blocking script debug --  related to the action of answering "No" to the 
dialog asking if you want to run a remoteDebug session,  just after installing 
the standalone on the phone… because I thought (have yet to test/reproduce… 
very tedious…) possibly that is at least one action that might toggle script 
debug mode to off (even though it appears checked?) and so your break point 
could possibly be ignored at that point and until you reboot LC?

Dunno, just was just fishing for possible recipes… 

but aha, gRevDevelopment, true:  the break point was "honored" Of course it 
starting stepping through a lot of IDE code, so I had to go back and set the 
gRevDevelopment to "false"  and now the break points work… 

….of course if it goes all the way back to 8.1.3 and 6, then it could be 
anything….

BR


Mike Kerner wrote:

Add a "breakpoint" line as the first line in the script
execute again
breakpoint still doesn't fire.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Mike Kerner via use-livecode]

This is something that got mixed up with the preferences, somehow.
Deleting the preferences file fixed it.

On Wed, Mar 8, 2017 at 7:09 PM, Dr. Hawkins via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On Wed, Mar 8, 2017 at 3:13 PM, J. Landman Gay via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > I haven't seen it in a while either. Craig is still on v6 though.
>
>
> Wow.
>
> I had so much problem with v6 and breakpoints that I never used it!
>
>
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Dr. Hawkins via use-livecode]

On Wed, Mar 8, 2017 at 3:13 PM, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:

> I haven't seen it in a while either. Craig is still on v6 though.


Wow.

I had so much problem with v6 and breakpoints that I never used it!


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[J. Landman Gay via use-livecode]

On 3/8/17 4:36 PM, Bob Sneidar via use-livecode wrote:

My recollection is that something in my app was causing a CTD
condition or a lockup where I had to force-quit, and after I
relaunched, the Script Debug Mode was disabled. When my app is
running normally I do not see this anomaly, and it may have been
addressed in a newed version.


I haven't seen it in a while either. Craig is still on v6 though.

--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Bob Sneidar via use-livecode]

My recollection is that something in my app was causing a CTD condition or a 
lockup where I had to force-quit, and after I relaunched, the Script Debug Mode 
was disabled. When my app is running normally I do not see this anomaly, and it 
may have been addressed in a newed version. 

Bob S


> On Mar 8, 2017, at 08:51 , dunbarx via use-livecode 
>  wrote:
> 
> This is SO annoying. I know one can get used to anything, but, sheesh.
> 
> Craig

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Dr. Hawkins via use-livecode]

On Wed, Mar 8, 2017 at 8:51 AM, dunbarx via use-livecode <
use-livecode@lists.runrev.com> wrote:

> This is SO annoying. I know one can get used to anything, but, sheesh.
>
>
We need to get used to getting used to new forms of the PCDs being ignored
. . .


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[dunbarx via use-livecode]

This is SO annoying. I know one can get used to anything, but, sheesh.

Craig



--
View this message in context: 
http://runtime-revolution.278305.n4.nabble.com/breakpoints-being-ignored-tp4712898p4712914.html
Sent from the Revolution - User mailing list archive at Nabble.com.

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Bob Sneidar via use-livecode]

OH! That is a different matter. I also ran into situations where the Script 
Debug Mode kept getting turned off. I haven't seen it in a long time. 

Bob S


> On Mar 7, 2017, at 18:12 , Mike Kerner via use-livecode 
>  wrote:
> 
> It's ignoring the "breakpoint" text, too, not just the dots.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Bob Sneidar via use-livecode]

There was a bug where these breakpoints were not triggering if the script 
before the dot was edited in such a way as to change the line number it was on. 
It was supposed to have been resolved, but I still see it from time to time. My 
solution is to unset and reset after each compile. If I have several I just use 
the breakpoint command. 

Bob S


> On Mar 7, 2017, at 17:36 , Mike Kerner via use-livecode 
>  wrote:
> 
> Explain this one:
> 8.1.3
> create a stack
> put a button on it
> add some script
> click in the margin to add a breakpoint - it shows grey with red border
> run the script
> breakpoint doesn't activate
> Add a "breakpoint" line as the first line in the script
> execute again
> breakpoint still doesn't fire.
> 
> -- 
> On the first day, God created the heavens and the Earth
> On the second day, God created the oceans.
> On the third day, God put the animals on hold for a few hours,
>   and did a little diving.
> And God said, "This is good."
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription 
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Dr. Hawkins via use-livecode]

On Tue, Mar 7, 2017 at 6:12 PM, Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:

> It's ignoring the "breakpoint" text, too, not just the dots.
>

I see that, but less frequently.  "Send in . . ." seems to be related to
that.


>
> Anyway, I trashed my preferences and it seems to be working, now.
>

Also, removing all of the red dots in a stack from time to time seems to
help.


-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Mike Kerner via use-livecode]

It's ignoring the "breakpoint" text, too, not just the dots.

Anyway, I trashed my preferences and it seems to be working, now.

On Tue, Mar 7, 2017 at 8:56 PM, Dr. Hawkins via use-livecode <
use-livecode@lists.runrev.com> wrote:

> On Tue, Mar 7, 2017 at 5:36 PM, Mike Kerner via use-livecode <
> use-livecode@lists.runrev.com> wrote:
>
> > breakpoint still doesn't fire.
>
>
> This is why I call them "Pirate Code Dots" (pad).
>
> The IDE sees them as merely advisory . . .
>
> And I'm again seeing the behavior that a red dot in a script that hasn't
> yet hit a breakpoint is often ignored.
>
> Or, with a break, a dialog, and another break, the break after the dialog
> is ignored.
>
> --
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: breakpoints being ignored

[Dr. Hawkins via use-livecode]

On Tue, Mar 7, 2017 at 5:36 PM, Mike Kerner via use-livecode <
use-livecode@lists.runrev.com> wrote:

> breakpoint still doesn't fire.


This is why I call them "Pirate Code Dots" (pad).

The IDE sees them as merely advisory . . .

And I'm again seeing the behavior that a red dot in a script that hasn't
yet hit a breakpoint is often ignored.

Or, with a break, a dialog, and another break, the break after the dialog
is ignored.

-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

breakpoints being ignored

[Mike Kerner via use-livecode]

Explain this one:
8.1.3
create a stack
put a button on it
add some script
click in the margin to add a breakpoint - it shows grey with red border
run the script
breakpoint doesn't activate
Add a "breakpoint" line as the first line in the script
execute again
breakpoint still doesn't fire.

-- 
On the first day, God created the heavens and the Earth
On the second day, God created the oceans.
On the third day, God put the animals on hold for a few hours,
   and did a little diving.
And God said, "This is good."
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[stephen barncard]

thank you Jacque!


Stephen Barncard
San Francisco Ca. USA

more about sqb  http://www.google.com/profiles/sbarncar
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Bob Sneidar]

Well as I said, the latest rendition seems very stable to me. No issues. 

Bob


On May 9, 2012, at 6:27 PM, stephen barncard wrote:

 Sadly, the only way I seem to be able to get the editor I want is to dive
 into GLX2 and try to find out what is wrong... but editing an editor is
 something I've never done before, and have a reluctance to try. Kudos to
 Mark for going in there.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Bob Sneidar]

Hmmm... This happens to me with the message window sometimes. Same cause?? 
After launching LC, if I open the Message Window and then switch to the multi 
line editor, no matter how big I made the window previously, the upper pane 
takes up the whole window and I have to resize it to get to the results pane. 
Once I do that, it is fine for the rest of the session. 

Bob


On May 9, 2012, at 7:54 PM, J. Landman Gay wrote:

 Stack-wide search works for me, I use it often. If you can describe what 
 didn't work maybe we can figure it out. There is one known glitch; the bottom 
 pane with the results doesn't display completely after the first search. You 
 have to resize the window the first time; then it pops into view and stays 
 there.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Mark Wieder]

stephen barncard stephenREVOLUTION2@... writes:

 Sadly, the only way I seem to be able to get the editor I want is to dive
 into GLX2 and try to find out what is wrong... but editing an editor is
 something I've never done before, and have a reluctance to try. Kudos to
 Mark for going in there.

Feel free to hack away at it. Writing a script editor isn't something I yearn to
do either. As project maintainer my job is mostly refactoring, fixing bugs where
they can be fixed (unfortunately there are a handful that can't) and
occasionally adding a feature that I want. There used to be a split screen
option where you could compare scripts, and the code seems to be there, but it
appears that I may have refactored that feature out of existence. I'll have to
see what it takes to bring it back.

-- 
 Mark Wieder




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Ken Corey]

On 08/05/2012 23:39, Colin Holgate wrote:

When you're next in the script editor, look at the bottom of the Debug menu. Is 
Script Debug Mode checked?


I've checked that the debug mode is checked on my environment.  It is.

I've noticed that there are situations where existing breakpoints from 
previous runs are ignored...so in the code I'm currently developing I've 
got this little voodoo routine:


Click on the blue circle in a square to stop debugging.
Change the code.
If I've got a breakpoint I care about, I must unclick it, and reclick it 
for it to break.
Click on a field in my app window (it's a Windows 7 machine, so that 
click should also go through to the field I'm clicking on.)

Click on the field again.  No input cursor.
Click on the script Editor.
Click on the field again. (now the field has a flashing cursor).

Test the code.

It doesn't stop me, and now I am doing it automatically...but still it's 
frustrating.


I'm on Windows 7 64 bit, Livecode 5.5.1 dp2 (though I've seen this 
behaviour previously, it subjectively seems to be getting worse).


-Ken

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Kay C Lan]

Hard type them, you'll have 100% success. The graphical ones are less than
perfect. Making big changes to a script, cutting or pasting large amounts
seems to confuse the script editor as to where the graphical breakpoints
were set and can simply leave a breakpoint in a portion of a script that
will not get hit.

Hard type them, comment them out if you are not sure if you will need them
again.

HTH

On Wed, May 9, 2012 at 2:57 PM, Ken Corey k...@kencorey.com wrote:

 On 08/05/2012 23:39, Colin Holgate wrote:

 When you're next in the script editor, look at the bottom of the Debug
 menu. Is Script Debug Mode checked?


 I've checked that the debug mode is checked on my environment.  It is.

 I've noticed that there are situations where existing breakpoints from
 previous runs are ignored...so in the code I'm currently developing I've
 got this little voodoo routine:

 Click on the blue circle in a square to stop debugging.
 Change the code.
 If I've got a breakpoint I care about, I must unclick it, and reclick it
 for it to break.
 Click on a field in my app window (it's a Windows 7 machine, so that click
 should also go through to the field I'm clicking on.)
 Click on the field again.  No input cursor.
 Click on the script Editor.
 Click on the field again. (now the field has a flashing cursor).

 Test the code.

 It doesn't stop me, and now I am doing it automatically...but still it's
 frustrating.

 I'm on Windows 7 64 bit, Livecode 5.5.1 dp2 (though I've seen this
 behaviour previously, it subjectively seems to be getting worse).

 -Ken


 __**_
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
 http://lists.runrev.com/**mailman/listinfo/use-livecodehttp://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Ken Corey]

On 09/05/2012 08:08, Kay C Lan wrote:

Hard type them, you'll have 100% success. The graphical ones are less than


By 'Hard type', do you mean to put breakpoint in my code?, or do you 
mean go to the breakpoints tab, right click, and select 'new breakpoint'?


-Ken

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Bob Sneidar]

I had a situation where certain kinds of errors would uncheck it for me! I had 
to check it every time before debugging. That problem has not happened in a 
long time though, and I am running the most recent versions of LC, GLX2 and 
PowerDebug. 

Bob


On May 8, 2012, at 4:04 PM, Mark Powell wrote:

 Yep, that be it.  I guess I unchecked it somehow sometime.  Thanks very
 much!
 
 On Tue, May 8, 2012 at 3:39 PM, Colin Holgate co...@verizon.net wrote:
 
 When you're next in the script editor, look at the bottom of the Debug
 menu. Is Script Debug Mode checked?
 
 
 
 
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode
 
 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your subscription 
 preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[stephen barncard]

Speaking of GLX2, I'd love to use it but I can't trust it not to implode
for no reason.  Sometimes it just gets lost or doesn't show handlers on the
left. Perhaps a memory leak? Errors are not reported properly or not at
all. And UNDO is completely broken. Bob, do you not have any issues with it?

Feature wise, there is no better editor for Livecode/Rev than GLX2. I
really want to use it but have been forced to go back to the native editor,
which has its own issues, which I will gripe about later. But at least it
doesn't lose  code.

Does GLX2 just work better with PowerDebug? I had not combined the two as I
thought it might just make it worse.


On Wed, May 9, 2012 at 8:41 AM, Bob Sneidar b...@twft.com wrote:

 I had a situation where certain kinds of errors would uncheck it for me! I
 had to check it every time before debugging. That problem has not happened
 in a long time though, and I am running the most recent versions of LC,
 GLX2 and PowerDebug.

 Bob


 On May 8, 2012, at 4:04 PM, Mark Powell wrote:

  Yep, that be it.  I guess I unchecked it somehow sometime.  Thanks very
  much!
 
  On Tue, May 8, 2012 at 3:39 PM, Colin Holgate co...@verizon.net wrote:
 
  When you're next in the script editor, look at the bottom of the Debug
  menu. Is Script Debug Mode checked?
 
 
 
 
  ___
  use-livecode mailing list
  use-livecode@lists.runrev.com
  Please visit this url to subscribe, unsubscribe and manage your
  subscription preferences:
  http://lists.runrev.com/mailman/listinfo/use-livecode
 
  ___
  use-livecode mailing list
  use-livecode@lists.runrev.com
  Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
  http://lists.runrev.com/mailman/listinfo/use-livecode


 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode




-- 



Stephen Barncard
San Francisco Ca. USA

more about sqb  http://www.google.com/profiles/sbarncar
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Bob Sneidar]

Actually, Mark Weider has done a lot to make GLX2 stable and better. The 
current version seems to be working really well. To my knowledge, PowerDebug 
has never been the source of any issues I have run into, but my memory is 
really bad so take that with a grain of salt. The issues I have had were also 
present in the vanilla debugger if I recall. I will go so far as to say that 
many of the features in the built-in editor and debugger were the result of 
Jerry's pioneering work in GLX2. PowerDebug is just the GLX2 debugger broken 
out as a separate plugin (correct me if I am wrong). 

I like PowerDebug for a few reasons, not the least of which is a hotkey for 
step over, into and what have you. I especially like usign the spacebar to step 
through code. I think their variable inspector is really well done as well. 
Being able to view the contents of an array has been especially useful to me 
and is primarily why I even use the LC arrays after becoming so used to 
numbered key style arrays. I also like the way tabs are managed, and the bread 
crumbs feature is genius. 

The problem of course, with this kind of editor and debugger, as Jerry has 
pointed out in the past, is that because it is done entirely in LC, the 
potential for breaking it when new versions of LC come out that make changes to 
the engine is always a factor. It was so much of an issue that Jerry opted for 
a different approach with Remo. He stores values of all the variables when he 
encounters a breakpoint. It takes some getting use to, and I used it for a 
while, but I personally favor the in-your-face stop executing and holler at me 
approach to debugging. 


On May 9, 2012, at 11:28 AM, stephen barncard wrote:

 Speaking of GLX2, I'd love to use it but I can't trust it not to implode
 for no reason.  Sometimes it just gets lost or doesn't show handlers on the
 left. Perhaps a memory leak? Errors are not reported properly or not at
 all. And UNDO is completely broken. Bob, do you not have any issues with it?
 
 Feature wise, there is no better editor for Livecode/Rev than GLX2. I
 really want to use it but have been forced to go back to the native editor,
 which has its own issues, which I will gripe about later. But at least it
 doesn't lose  code.
 
 Does GLX2 just work better with PowerDebug? I had not combined the two as I
 thought it might just make it worse.


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Mark Wieder]

Bob Sneidar bobs@... writes:

 
 I had a situation where certain kinds of errors would uncheck it for me! I had
to check it every time before
 debugging. That problem has not happened in a long time though, and I am
running the most recent versions of
 LC, GLX2 and PowerDebug. 

This can happen if an error occurs in an IDE stack... at times the IDE will
disable debug mode to keep you out of trouble. In PowerDebug I explicitly keep
debug mode on (and re-enable it when necessary) to prevent this situation from
happening.

-- 
 Mark Wieder



___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Mark Wieder]

Bob Sneidar bobs@... writes:

 
 Actually, Mark Weider has done a lot to make GLX2 stable and better.

Thanks!

 The current version seems to be working
 really well. To my knowledge, PowerDebug has never been the source of any
issues I have run into, but my
 memory is really bad so take that with a grain of salt. The issues I have had
were also present in the vanilla
 debugger if I recall. I will go so far as to say that many of the features in
the built-in editor and debugger
 were the result of Jerry's pioneering work in GLX2. PowerDebug is just the
GLX2 debugger broken out as a
 separate plugin (correct me if I am wrong).

I originally broke the debugger out as a separate plugin because mixing the code
together was starting to get hopelessly complicated. And I wanted to have the
debugger work with Remo. There are only a few points of contact between the
script editor and the debugger, so it was easy enough to pull these out into an
api. But PowerDebug rapidly took on a life of its own with added features and
more robustness, especially as it evolved the ability to debug standalone
applications.
 
 
 I like PowerDebug for a few reasons, not the least of which is a hotkey for
step over, into and what have you. I
 especially like usign the spacebar to step through code. I think their
variable inspector is really well
 done as well. Being able to view the contents of an array has been especially
useful to me and is primarily
 why I even use the LC arrays after becoming so used to numbered key style
arrays. I also like the way tabs are
 managed, and the bread crumbs feature is genius.

My favorite features of GLX2 are breadcrumbs, handler links, and folders. I
really miss all those when I have to work in the IDE's script editor. OTOH, the
IDE has better search capabilities. 

 The problem of course, with this kind of editor and debugger, as Jerry has
pointed out in the past, is that
 because it is done entirely in LC, the potential for breaking it when new
versions of LC come out that make
 changes to the engine is always a factor.

groan
Quite right. And the changes, when they come, aren't usually documented, forcing
a mad scramble and regression test with each new release.
/groan

Back on topic, the soft breakpoints set in the editor are stored as custom
properties of the target stack and sometimes don't align properly any more with
the script text. Recompiling the script *should* fix this, but doesn't always do
that. Removing the custom property and setting the breakpoints again should 
work.

-- 
 Mark Wieder


___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[stephen barncard]

Agreed! and thanks to Jerry for opening up the code to OSS.  I didn't mean
to diminish Mark's work on GLX2, I'm just frustrated with the current state
of affairs with editors in Livecode in general. I've been spoiled by and
used to Remo for years and have been comfortable with it, considered it the
best editor.

If you want software to break, give it to me, I seem to break everything.
but here's the deal: we have 4 choices for editors, all with downsides:

1. The native editor is stable, but has oddities that annoy, like that
unnecessary double-enter compile-and-close window thing, or the lack of a
charcoal motif, that is easier on the eyes of the myopic. I couldn't get
the stack-wide search to work. Navigation is still a struggle on big
projects. And I'd like to be able to open a second window to compare code.
But none of the editors do that. This editor has worked basically the same
since 2001.

2. Remo won't work in Livecode 5.02+ and is MIA, and I assume dead at this
point. No website exists and no word from Jerry.

3. GLX2  - am I the only one that has these problems mentioned earlier?

4. the BBEDIT plugin thing that Trevor created eons ago. It works, but
doesn't have any navigation for big projects.

Sadly, the only way I seem to be able to get the editor I want is to dive
into GLX2 and try to find out what is wrong... but editing an editor is
something I've never done before, and have a reluctance to try. Kudos to
Mark for going in there.

On Wed, May 9, 2012 at 12:32 PM, Mark Wieder mwie...@ahsoftware.net wrote:

 Bob Sneidar bobs@... writes:

 
  Actually, Mark Weider has done a lot to make GLX2 stable and better.

 Thanks!

  The current version seems to be working
  really well. To my knowledge, PowerDebug has never been the source of any
 issues I have run into, but my
  memory is really bad so take that with a grain of salt. The issues I
 have had
 were also present in the vanilla
  debugger if I recall. I will go so far as to say that many of the
 features in
 the built-in editor and debugger
  were the result of Jerry's pioneering work in GLX2. PowerDebug is just
 the
 GLX2 debugger broken out as a
  separate plugin (correct me if I am wrong).

 I originally broke the debugger out as a separate plugin because mixing
 the code
 together was starting to get hopelessly complicated. And I wanted to have
 the
 debugger work with Remo. There are only a few points of contact between the
 script editor and the debugger, so it was easy enough to pull these out
 into an
 api. But PowerDebug rapidly took on a life of its own with added features
 and
 more robustness, especially as it evolved the ability to debug standalone
 applications.

 
  I like PowerDebug for a few reasons, not the least of which is a hotkey
 for
 step over, into and what have you. I
  especially like usign the spacebar to step through code. I think their
 variable inspector is really well
  done as well. Being able to view the contents of an array has been
 especially
 useful to me and is primarily
  why I even use the LC arrays after becoming so used to numbered key style
 arrays. I also like the way tabs are
  managed, and the bread crumbs feature is genius.

 My favorite features of GLX2 are breadcrumbs, handler links, and folders. I
 really miss all those when I have to work in the IDE's script editor.
 OTOH, the
 IDE has better search capabilities.

  The problem of course, with this kind of editor and debugger, as Jerry
 has
 pointed out in the past, is that
  because it is done entirely in LC, the potential for breaking it when new
 versions of LC come out that make
  changes to the engine is always a factor.

 groan
 Quite right. And the changes, when they come, aren't usually documented,
 forcing
 a mad scramble and regression test with each new release.
 /groan

 Back on topic, the soft breakpoints set in the editor are stored as custom
 properties of the target stack and sometimes don't align properly any more
 with
 the script text. Recompiling the script *should* fix this, but doesn't
 always do
 that. Removing the custom property and setting the breakpoints again
 should work.

 --
  Mark Wieder


 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode




-- 



Stephen Barncard
San Francisco Ca. USA

more about sqb  http://www.google.com/profiles/sbarncar
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[J. Landman Gay]

On 5/9/12 8:27 PM, stephen barncard wrote:


1. The native editor is stable, but has oddities that annoy, like that
unnecessary double-enter compile-and-close window thing, or the lack of a
charcoal motif, that is easier on the eyes of the myopic. I couldn't get
the stack-wide search to work. Navigation is still a struggle on big
projects. And I'd like to be able to open a second window to compare code.
But none of the editors do that. This editor has worked basically the same
since 2001.


I think you can get close to what you want in the native editor, with 
the exception of #1 which I wouldn't like to see change. The MC editor 
compiles and closes immediately on Enter (though you can use Cmd-L to 
compile without closing.) I'm usually working on a script and testing as 
I go, and I don't want to keep re-opening the script for each change. So 
I guess that part is subjective. I could have sworn there used to be a 
keyboard combo to both compile and close the editor in one go but I 
can't find it now.


Charcoal motif: You can set the background color of the editor in prefs. 
I guess if you want to change the text color to white you'd need to set 
that in the main template, which I'm having trouble locating right now. 
I think this may do it:


  set the textcolor of fld script of grp editor of stack 
revNewScriptEditor to white


Stack-wide search works for me, I use it often. If you can describe what 
didn't work maybe we can figure it out. There is one known glitch; the 
bottom pane with the results doesn't display completely after the first 
search. You have to resize the window the first time; then it pops into 
view and stays there.


Navigation: I do it via the App Browser. I always keep it open, it's the 
fastest way to jump around. Double-click any card in any stack and there 
you are. I also like that I can edit the script or properties of any 
object from there, regardless of whether I'm currently on that card or 
even in that stack.


You can open more than one editor window. Right-click on the script's 
tab in the editor and choose move to new window.



--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software   | http://www.hyperactivesw.com

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Kay C Lan]

Sorry for the slow reply, but yes, type the word 'breakpoint' into your
scripts. I got sick and tired of Rev skipping graphical breakpoints that I
just type them in now. NEVER had one missed since.

On Wed, May 9, 2012 at 4:12 PM, Ken Corey k...@kencorey.com wrote:

 On 09/05/2012 08:08, Kay C Lan wrote:

 Hard type them, you'll have 100% success. The graphical ones are less than


 By 'Hard type', do you mean to put breakpoint in my code?, or do you
 mean go to the breakpoints tab, right click, and select 'new breakpoint'?


 -Ken

 __**_
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
 http://lists.runrev.com/**mailman/listinfo/use-livecodehttp://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Breakpoints being ignored

[Mark Powell]

Breakpoints are not being recognized all of a sudden.  Something
do doubt is corrupted and I'd be interested in knowing if there is a clean
fix.

Test case:  I create a brand new stack, with a button scripted

on mouseup
  answer 1
  breakpoint
  answer 2
end mouseup

I get the two answer dialogs, but without the script breaking at the
breakpoint.

Any tips appreciated!

Mark
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Colin Holgate]

When you're next in the script editor, look at the bottom of the Debug menu. Is 
Script Debug Mode checked?




___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

Re: Breakpoints being ignored

[Mark Powell]

Yep, that be it.  I guess I unchecked it somehow sometime.  Thanks very
much!

On Tue, May 8, 2012 at 3:39 PM, Colin Holgate co...@verizon.net wrote:

 When you're next in the script editor, look at the bottom of the Debug
 menu. Is Script Debug Mode checked?




 ___
 use-livecode mailing list
 use-livecode@lists.runrev.com
 Please visit this url to subscribe, unsubscribe and manage your
 subscription preferences:
 http://lists.runrev.com/mailman/listinfo/use-livecode

___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode