On Tue, Jul 25, 2017 at 1:15 PM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Since clearing all breakpoints (including the one for line 5000 of the
> revDebugWhatchamacallit script) the red dot breakpoints seem to be behaving
> normally again. Curious.
>
> I have long fo
Since clearing all breakpoints (including the one for line 5000 of the
revDebugWhatchamacallit script) the red dot breakpoints seem to be behaving
normally again. Curious.
Bob S
> On Jul 25, 2017, at 09:34 , Bob Sneidar wrote:
>
> Not that it matters, but I opened that script and then clear
On 7/24/17 6:05 PM, Monte Goulding via use-livecode wrote:
On 25 Jul 2017, at 8:37 am, J. Landman Gay via use-livecode
wrote:
You can debug these using the remote debugger only.
Does that still work? It never asks me any more.
It should. If it doesn’t for you could you bug report it ple
On 07/24/2017 03:31 PM, Alex Tweedly via use-livecode wrote:
I keep getting caught by this - setting a breakpoint in a handler which
is (indirectly) called from a resizeStack, and LC gets completely
frozen and needs to be Force-quit.
Um... once again... PowerDebug to the rescue.
Doesn't igno
On 07/25/2017 09:26 AM, Bob Sneidar via use-livecode wrote:
OK here is a perfect example. I get on one of the lines,
stack "/Applications/LiveCode Business
8.1.5.app/Contents/Tools/Toolset/libraries/revdebuggerlibrary.livecodescript",5000
Problem: There are not 5000 lines in that script when I
In an unrelated incident, I think I just found one way explicit variables can
get set. I set gRevDevelopment to true, then set it back to false when I was
done. Then I attempted to save a script and the predictable occured. (Yes I
know how to set it back.)
Bob S
> On Jul 25, 2017, at 09:26 ,
Not that it matters, but I opened that script and then cleared all breakpoints.
Now I have no breakpoints set, so let's see if it behaves any differently.
Bob S
> On Jul 25, 2017, at 09:26 , Bob Sneidar via use-livecode
> wrote:
>
> OK here is a perfect example. I get on one of the lines,
OK here is a perfect example. I get on one of the lines,
stack "/Applications/LiveCode Business
8.1.5.app/Contents/Tools/Toolset/libraries/revdebuggerlibrary.livecodescript",5000
Problem: There are not 5000 lines in that script when I go to edit it. Further
I have never edited that script!
B
Hmmm... good thought. It may have been a datagrid script I was looking at.
Besides my database library, I am not using behaviors a lot. I'll give those
other things a try.
Bob S
> On Jul 25, 2017, at 08:56 , Mark Wieder via use-livecode
> wrote:
>
> As a last resort, if you're seeing line
On 07/25/2017 08:09 AM, Bob Sneidar via use-livecode wrote:
Thanks Monte, but I do not use modal any more than I can help it. This is
happening in virtually every script I have. As I mentioned, I had one script
where the breakpoints pane reported that the script had a breakpoint on line 6
hund
Thanks Monte, but I do not use modal any more than I can help it. This is
happening in virtually every script I have. As I mentioned, I had one script
where the breakpoints pane reported that the script had a breakpoint on line 6
hundred something, and there have never been any more that 200 lin
e-livecode-boun...@lists.runrev.com] On Behalf
Of Alex Tweedly via use-livecode
Sent: Monday, July 24, 2017 6:31 PM
To: use-livecode@lists.runrev.com
Cc: Alex Tweedly
Subject: Re: Ethereal Breakpoints
I keep getting caught by this - setting a breakpoint in a handler which is
(indirectly) called from a resi
> On 25 Jul 2017, at 8:31 am, Alex Tweedly via use-livecode
> wrote:
>
> You know, I really wish it could be (even) more helpful : in particular,
> ignoring breakpoints within handlers called from a resizeStack handler.
>
> I keep getting caught by this - setting a breakpoint in a handler wh
> On 25 Jul 2017, at 8:37 am, J. Landman Gay via use-livecode
> wrote:
>
>> You can debug these using the remote debugger only.
>
> Does that still work? It never asks me any more.
It should. If it doesn’t for you could you bug report it please.
Cheers
Monte
On 7/24/17 4:37 PM, Monte Goulding via use-livecode wrote:
You can debug these using the remote debugger only.
Does that still work? It never asks me any more.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
__
On 24/07/2017 22:37, Monte Goulding via use-livecode wrote:
There are some cases where breakpoints are deliberately ignored. Any
breakpoints when there is modal stack open and in resizeStack and moveStack
handlers.
You know, I really wish it could be (even) more helpful : in
particular, ign
There are some cases where breakpoints are deliberately ignored. Any
breakpoints when there is modal stack open and in resizeStack and moveStack
handlers. You can debug these using the remote debugger only.
Cheers
Monte
> On 25 Jul 2017, at 1:37 am, Bob Sneidar via use-livecode
> wrote:
>
>
With me, I place a red dot, find an error in the script, edit the script
neither adding nor deleting any lines, save script, red dot does not wander,
but also does not break code execution. It just executed past it.
I think this started with the unicode update. I will try copying my code to a
all of the above experiences confirmed here.. it's so bad sometimes I remove
all break points from the menu, save everything, shut down and start add manual
breakpoint
in the actual code. with my text editor (using 85% script only
text.livecodescripts now)
then reboot and pray.
such a nuis
And I should clarify, the fix is for the “delayed moving” of break points. Not
the “ethereal” issue ;-)
Bob
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
prefere
>
> I haven’t looked at the code that tries to keep the like paired with the
> breakpoint but my gut feeling is to do it right you would want to set some
> metadata on the line of the field and then look for it when updating the
> gutter. I’ll try and find some time to take a look into it.
>
> On 22 Jul 2017, at 9:55 am, J. Landman Gay via use-livecode
> wrote:
>
> I'm not having any trouble with the breakpoints per se but if you edit the
> script with the dots in place they tend to migrate. When that happens you
> don't always notice and it acts like they aren't working.
I have
On Fri, Jul 21, 2017 at 4:55 PM, J. Landman Gay via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I'm not having any trouble with the breakpoints per se but if you edit the
> script with the dots in place they tend to migrate. When that happens you
> don't always notice and it acts like t
I'm not having any trouble with the breakpoints per se but if you edit the
script with the dots in place they tend to migrate. When that happens you
don't always notice and it acts like they aren't working.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software
On Fri, Jul 21, 2017 at 2:47 PM, Peter Bogdanoff via use-livecode <
use-livecode@lists.runrev.com> wrote:
On Mac, you never know for sure if a BP will trigger.
>
I took to calling them "Pirate Code Dots" for a reason.
In all fairness, they got *MUCH* better a few months ago, and now usually
work
Heh heh. One of my breakpoints says group "dgDevices" line 568. There are 136
lines in that script. There have never been more that 200.
Bob S
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscrib
Thanks Peter that is also my experience, although like I said at one point it
seemed to be working so I started using them again. As is the red dot
breakpoints are completely unusable.
Bob S
> On Jul 21, 2017, at 14:47 , Peter Bogdanoff via use-livecode
> wrote:
>
> On Mac, you never know
On Mac, you never know for sure if a BP will trigger.
Then you may also see spurious BPs listed in the Breakpoints tab below, or in
the script above.
Peter Bogdanoff
> On Jul 21, 2017, at 2:31 PM, Ralph DiMola via use-livecode
> wrote:
>
> Interesting, I haven't had a problem with red dots.
Interesting, I haven't had a problem with red dots. I'm on Win 10 / 8.1.5.
In fact if I set BP save, close LC, reopen and launch my stack the script
breaks. BPs are saved in the stack I guess.
Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
-Original Message
29 matches
Mail list logo