Mike-
Sunday, January 15, 2012, 8:56:29 AM, you wrote:
> TextWrangler found Gremlins! Once removed, all seems to be back to normal.
Yay!
--
-Mark Wieder
mwie...@ahsoftware.net
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please vi
Mark-
Sunday, January 15, 2012, 6:35:32 AM, you wrote:
> Surely, stacks can get corrupted, but I have seen this happen
> only once during the past few years. The reason was that the stack
> was moved from Windows to Mac and opened, while text fields and
> scripts were somehow not re-encoded.
I h
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 th
TextWrangler found Gremlins! Once removed, all seems to be back to normal.
Mark, many thanks!
Regards,
Mike
On 2012-01-15, at 11:45 AM, Michael Doub wrote:
>> I don't understand "but I can add put statements... NOT in the
>> getProp/setProp handlers". What do you mean?
>
>
> When I
> I don't understand "but I can add put statements... NOT in the
> getProp/setProp handlers". What do you mean?
When I was not able to set a breakpoint. I started to selectively include
"Put xxx" so I could track the progress of app. I included put statement in
both the handlers and in the
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
breakpoin
Hi Mike,
The debugger is not reliable to begin with, but there might be a valid reason
why you can't set a breakpoint, e.g. because that line is commented out.
I don't understand "but I can add put statements... NOT in the getProp/setProp
handlers". What do you mean?
It is possible that you ha
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 beh
Hi Mike,
Custom properties are very useful and reliable but will cause problems if:
1) you use them to save text to be displayed on multiple platforms
2) you want to save them as part of your standalone
Solve (1) by storing text as unicode but keep in mind that this may still not
work on PowerMa
Are there conditions where getProp/setProp should not be used? have seen
multiple instances where the setProp message does not seem to be recieved.
What is even more strange is the fact that sometimes it works then for no
reason it stops.
These constructs are much easer to use than sending
10 matches
Mail list logo
