...@evergreeninfo.net
-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of Bob Sneidar via use-livecode
Sent: Monday, June 07, 2021 11:12 AM
To: How to use LiveCode
Cc: Bob Sneidar
Subject: Re: Finding out what changes a custom property
Oooh never thought
Oooh never thought of that... so setprops get called before a property gets
set?
Bob S
> On Jun 6, 2021, at 14:10 , Curry Kenworthy via use-livecode
> wrote:
>
>
> Paul:
>
> > Is there an debugger feature or tip or trick anyone has
> > that can do the equivalent of set a break point when
Hi Paul,
In the development menu, open 'message watcher'. That's helped me with
exactly what you are looking for too. Fantastic tool.
Sean
On Sun, 6 Jun 2021 at 21:21, Paul Dupuis via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I have a stack with a custom property, hrStart.
>
>
Paul:
> Is there an debugger feature or tip or trick anyone has
> that can do the equivalent of set a break point when a property
> is changed and let me see the executionContexts
> to tell what the heck is changing it!
Add a setprop with either a breakpoint and/or the executionContexts?
I have a stack with a custom property, hrStart.
Somewhere is miles of code and messages flying everywhere, something is
changing it that shouldn't.
Is there an debugger feature or tip or trick anyone has that can do teh
equivalent of set a break point when a property is changed and let me
