On Wed, 20 Jun 2007 00:43:18 -0700, Scott Rossi wrote:
> Any ideas on how to troubleshoot this?
I'm betting it's something in the mouseMove handler itself - do you
have any lines that use "the target" in your mouseMove handler? THe
reason I say this is I've been caught a similar way with an err
It seems something unexpected is happening.
Can you set the property from the message box?
Does this happen in every instance?
Can you "put the uCurrObj of me into msg"? and get something that can be
evaluated/ (that is, non-binary?)
Try 'exit to top', since the calling handler may be expecting a
On Jun 20, 2007, at 3:34 AM, Stephen Barncard wrote:
watch out for the vague "me" reference and try something more
absolute, like the id or name of the object you are calling 'me'.
Sometimes getting the id of me or the owner of me works.
What's vague about "me"? As far as I'm concerned, "m
Scott: I don't know if this will help but try this:
watch out for the vague "me" reference and try something more
absolute, like the id or name of the object you are calling 'me'.
Sometimes getting the id of me or the owner of me works.
I'm wondering if anyone has a suggestion for finding
I'm wondering if anyone has a suggestion for finding a script error when the
error dialog is (probably not) reporting the true cause of the error.
I have a card script handler that is called multiple times from a mouseMove
handler. It looks something like this:
on unselectObjects
if the uCurrO
