Hi.
Mark Wieder via use-livecode wrote
> LOL. That's an utterly bizarre workflow, but I'm glad it works.
> I'm filing that away somewhere if I ever have to record the screen on
> Windows.
That's actually the most nasty method I ever read of. You may as well:
1. Press "Print" on your keyboard,
On 8/12/19 7:29 PM, Richard Gaskin via use-livecode wrote:
Mark Wieder wrote:
> A stack's breakpoints are stored in the cREVGeneral["breakpoints"] of
> the stack itself...
When did this happen? IIRC for most of MC/LC's life the breakpoints
were an engine-level stack property.
"the
Mark Wieder wrote:
> A stack's breakpoints are stored in the cREVGeneral["breakpoints"] of
> the stack itself...
When did this happen? IIRC for most of MC/LC's life the breakpoints
were an engine-level stack property.
--
Richard Gaskin
Fourth World Systems
Software Design and Development
On 8/12/19 10:41 AM, J. Landman Gay via use-livecode wrote:
On 8/12/19 8:32 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
Switching to hard coded "breakpoint"
It a tricking thing "clearing" those
I sometimes use Matthias' method but since the crash report I've started
marking my
On 8/12/19 1:19 PM, Martin Koob via use-livecode wrote:
Sometimes it works beautifully at each breakpoint the script stops. other times
it doesn’t stop at all or stops only at open scripts. Also I have the problems
of not being able to always delete the red dots. In a bit more detail here is
There was a post earlier where someone mentioned that Panos is onto this one
and is looking into it.
Bob S
> On Aug 12, 2019, at 13:19 , Martin Koob via use-livecode
> wrote:
>
> I just got used to the flakiness of the red dot breakpoints so adapted my
> workflow with workarounds to use
I just got used to the flakiness of the red dot breakpoints so adapted my
workflow with workarounds to use them.
When I am debugging I want to follow through different objects that the script
jumps to. I have the red breakpoints in the different objects, i.e. Button ->
group-> card->
On 8/12/19 8:32 AM, Sannyasin Brahmanathaswami via use-livecode wrote:
Switching to hard coded "breakpoint"
It a tricking thing "clearing" those
I sometimes use Matthias' method but since the crash report I've started
marking my breakpoints with a special comment like this:
> Switching to hard coded "breakpoint"
> It a tricking thing "clearing" those
Currently i am doing it this way.
At the first line of a script i have "put TRUE into tDebug"
and my breakpoints are set this way.
"if tDebug then breakpoint"
If i don´t want them to be active anymore i
I've been debugging code and "fell" into old habit of using "red dot
breakpoints"
-- crashing every 10 minutes! No recipe...
I guess I don't need to report this, but just saying "it a real pain"
Switching to hard coded "breakpoint"
It a tricking thing "clearing" those
BR
J. Landman Gay
Well interestingly, after clearing all my breakpoints, I have not had one CTD
in 2 hours! Yeah, I think Panos is on to something. It explains also why the
standalones I build are not crashing in the same way.
Bob S
> On Aug 2, 2019, at 09:02 , J. Landman Gay via use-livecode
> wrote:
>
>
That sounds related somehow. On Mac, you're more apt to get a crash rather
than just a visual glitch. What happens if you use the Developer menu to
clear all breakpoints? Same thing?
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On
It's a display bug. Quit LC, relaunch, watchpoint gone.
Bob S
> On Aug 2, 2019, at 08:29 , Bob Sneidar via use-livecode
> wrote:
>
> Hmmm... I did have a watch point set... I will clear all my breakpoints and
> see what happens.
>
> Bob S
>
>
>> On Aug 2, 2019, at 08:26 , J. Landman
Well I just discovered a new bug! I cannot delete a watch point. Richt-click
delete nothing happens.
Bob S
> On Aug 2, 2019, at 08:29 , Bob Sneidar via use-livecode
> wrote:
>
> Hmmm... I did have a watch point set... I will clear all my breakpoints and
> see what happens.
>
> Bob S
>
Hmmm... I did have a watch point set... I will clear all my breakpoints and see
what happens.
Bob S
> On Aug 2, 2019, at 08:26 , J. Landman Gay via use-livecode
> wrote:
>
> Panos has diagnosed at least part of the problem. It has to do with red dot
> breakpoints. Using the breakpoint
Panos has diagnosed at least part of the problem. It has to do with red dot
breakpoints. Using the breakpoint command instead may (will?) avoid the crash.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On August 1, 2019 4:22:57 PM Bob
Ok strange, i almost never have a crash. I had once, and made a bug
report a time ago, it was when the message box open and the message
watcher. I thought it was fixed back then.
Sometimes it hangs when pushing to device with test, but that's probably
due to a wacky usb cable and it looses a
It depends. Sometimes debugging stepping through code. Hovering over a variable
to see it's value. Other times just working in my app. Recently I have been
adding files to the database. I have a method where I drag files from the
Finder onto a button or field, and import the files as binary
Is it happening after debugging in the script editor? If so, please add
comments and any crash logs to this bug report where they are being collected:
https://quality.livecode.com/show_bug.cgi?id=22130
Include an explanation of what you were doing at the time and any other
info that might
On 8/1/19 5:10 PM, Pi Digital via use-livecode wrote:
On Windows 10 With LC open
Press the windows key and ‘g’ at the same time. This opens the GameBar dialogue
(it’s meant for games but works equally well for any app).
Check the ‘yes, this is a game’ box.
LOL. That's an utterly bizarre
If you are on macOS you have one built in to QuickTime. File>NewScreenRecording
On Windows 10 With LC open
Press the windows key and ‘g’ at the same time. This opens the GameBar dialogue
(it’s meant for games but works equally well for any app).
Check the ‘yes, this is a game’ box.
Click
Hi
There are others who are seeing Crash to Desktop while debugging.
There is a bug report where people can upload their crash logs to. You should
upload yours there to give the LC team more data to work with, especially if
you can reliably reproduce it.
On Aug 1, 2019, at 2:26 PM, JJS via use-livecode
wrote:
>
> what are you doing, or what is running when that happens?
When I’ve seen it with the dp and rc, it tends to be after I move objects, or
perhaps copy and paste objects, and then a delay, a brief moment of returning
to apparent
what are you doing, or what is running when that happens?
Op 1-8-2019 om 23:21 schreef Bob Sneidar via use-livecode:
Hi all. Just letting everyone know I am crashing to desktop in 9.5.0 "stable"
(LOL) about very 10 minutes now. No bueno. Going back to 9.0.5.
Bob S
Screen Record it first and post up to the quality site. #metoo
Sean Cole
Pi Digital Prod Ltd
> On 1 Aug 2019, at 22:21, Bob Sneidar via use-livecode
> wrote:
>
> Hi all. Just letting everyone know I am crashing to desktop in 9.5.0 "stable"
> (LOL) about very 10 minutes now. No bueno. Going
Hi all. Just letting everyone know I am crashing to desktop in 9.5.0 "stable"
(LOL) about very 10 minutes now. No bueno. Going back to 9.0.5.
Bob S
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe,
26 matches
Mail list logo
