Reliability of setProp/getProp

[Michael Doub]

Thanks Bernard, 

I know that I am not locking messages as I have not learned when and when not to do such a thing.  Another on my list of things to learn about.

I have started using the hard breakpoints.

Regards,
    Mike



On 2012-01-15, at 9:44 AM, Bernard Devlin wrote:

> Are you locking the message path in some other handler (e.g. maybe one
> that is done with 'send in time').  That might explain intermittent
> behaviour.
> 
> Also, there is a 'breakpoint' command that you can literally type as a
> line in your handler.  I've often (like almost always) seen red dot
> breakpoints that will work the first time a piece of code is
> breakpointed, but will not work if a change is made to the script, and
> then the actions run again to get to that breakpoint. However, the
> 'breakpoint' command has never not worked for me.
> 
> Bernard
> 
> On Sun, Jan 15, 2012 at 2:01 PM, Michael Doub <mike at doub.com> wrote:
>> I have a group "Pointer" that is made of 2 graphic objects.  Within the script of group "Pointer", I have:
>> 
>> setprop thecolor newcolor
>> getProp thecolor
>> setprop finger newloc
>> 
>> I am not using them to set any persistent state but to control the color and location of the object itself.
>> 
>> When this behaviour starts, I am not able to set a breakpoints,
> 
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode