Re: Setting conditional breakpoints

2019-06-24 Thread J. Landman Gay via use-livecode
I doubt you're thick, Lagi. :) As I mentioned before, I'm having a lot of trouble with breakpoints lately. Also, there's a difference between a breakpoint and a watch, and I rarely use watches because they aren't universally applicable. I do use conditional breakpoints though. A watch is

Re: Setting conditional breakpoints

2019-06-24 Thread Mark Wieder via use-livecode
On 6/24/19 10:38 AM, Dr. Hawkins via use-livecode wrote: But how about defining ”zetProp” as a stack (or whatever) property, and making the code changes I mentioned? Yep - that's the way I work around it as well: setprop _visible pValue set the visible of me to pValue end _visible on

Re: Setting conditional breakpoints

2019-06-24 Thread Dr. Hawkins via use-livecode
On Jun 24, 2019, at 10:32 AM, Mark Wieder via use-livecode wrote: > > Unfortunately, it's still not possible to use setProp and getProp handlers > with built-in properties, so catching a change to the visible of an object > won't work. It's been in bugzilla for 14 years now. > >

Re: Setting conditional breakpoints

2019-06-24 Thread Mark Wieder via use-livecode
On 6/24/19 9:00 AM, doc hawk via use-livecode wrote: > Anyway, if you use setProp handlers instead of directly setting properties, you could stick a little red PCD in *that* handler. Unfortunately, it's still not possible to use setProp and getProp handlers with built-in properties, so

Re: Setting conditional breakpoints

2019-06-24 Thread doc hawk via use-livecode
On Jun 24, 2019, at 8:11 AM, Bob Sneidar via use-livecode wrote: > > True, but I need itto break AT the line of code that changes a property of a > stack. If there is a script running while when the send in time command is > due, the existing script will continue to run, THEN at the first

Re: Setting conditional breakpoints

2019-06-24 Thread Bob Sneidar via use-livecode
True, but I need itto break AT the line of code that changes a property of a stack. If there is a script running while when the send in time command is due, the existing script will continue to run, THEN at the first idle, the send in time will run. Bob S > On Jun 21, 2019, at 16:51 , Tom

Re: Setting conditional breakpoints

2019-06-24 Thread Lagi Pittas via use-livecode
Hi Jacque, It never worked before and I couldn't get it to work today. I can't be that thick can I? If the "incantation" means I can't get it work (especially the delete - the breakpoints i set would not remove however I clicked) easily then I would presume there are some people as dumb as me

Re: Setting conditional breakpoints

2019-06-21 Thread Tom Glod via use-livecode
oh you can open up the engine to do other handlers by using "in time" I use it all the time..I have a message checking hotkeys clipboard changes and it works beautifully. on CheckIfVisible if the visible of defaultstack = true then send "CheckIfVisible" to defaultstack in 100

Re: Setting conditional breakpoints

2019-06-21 Thread J. Landman Gay via use-livecode
Set a breakpoint, right click it, choose condition, and fill out the dialog. That's how I usually do it. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On June 21, 2019 5:34:30 PM Bob Sneidar via use-livecode wrote: In the breakpoints

Re: Setting conditional breakpoints

2019-06-21 Thread Bob Sneidar via use-livecode
That would be true if the engine was multithreaded. As it is, I am trying to find the line of script that is changing the property, and until the script terminates, no other script can run. Bob S > On Jun 21, 2019, at 15:56 , Tom Glod via use-livecode > wrote: > > well it can be done just

Re: Setting conditional breakpoints

2019-06-21 Thread Bob Sneidar via use-livecode
https://quality.livecode.com/show_bug.cgi?id=22203 > On Jun 21, 2019, at 15:46 , Bob Sneidar via use-livecode > wrote: > > OK looks like setting a breakpoint on a property change like the visible of a > stack can't be done. Might be a nice addition though. Let's say you have a > custom

Re: Setting conditional breakpoints

2019-06-21 Thread Tom Glod via use-livecode
well it can be done just have a handler that checks the condition every x millisecondsif true ...breakpoint..if falseresend message. On Fri, Jun 21, 2019 at 6:46 PM Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > OK looks like setting a breakpoint on a property

Re: Setting conditional breakpoints

2019-06-21 Thread Bob Sneidar via use-livecode
OK looks like setting a breakpoint on a property change like the visible of a stack can't be done. Might be a nice addition though. Let's say you have a custom property that keeps getting corrupted (by which I mean it contains bad data) and you want to catch it in the act. Wouldn't it be nice

Re: Setting conditional breakpoints

2019-06-21 Thread Bob Sneidar via use-livecode
In the breakpoints tab of the script editor, if you right click the lower pane, you can create conditional breakpoints. For instance if the value of a variable is something. I have never gotten them to work, and I find I am needing this more and more. Bob S > On Jun 21, 2019, at 15:26 ,

Re: Setting conditional breakpoints

2019-06-21 Thread dunbarx--- via use-livecode
Not sure what you could mean. on mouseUp  if the mouseLoc is within the rect of btn 3 then breakPoint   if the visible  of btn 3 then breakPoint   if the... Surely I am missing this. Craig -Original Message- From: Bob Sneidar via use-livecode To: How to use LiveCode Cc: Bob Sneidar