More Problem with Player Object in Library Stack
Dave
dave at looktowindward.com
Tue Jun 19 05:19:59 EDT 2007
On 19 Jun 2007, at 10:10, Michael Binder wrote:
> Hi Dave, you wrote:
>
>> breakpoint
>> put the short name of this stack into myCallingStack
>> show me
>> go stack the (short name of me)
>> set the fileName of player "PlayerThumbnail" of me to
>> theMovieFilePathName
>>
>> The file is valid and plays find in another player object.
>>
>> Any ideas on how to work around this?
>
> Reading your code, I am a little confused about 'this' and
> 'me'. In my (admittedly limited) experience, rev also gets
> confused about these things. What happens if you try this:
>
> breakpoint
> put the short name of stack "myStack" into myCallingStack
> show stack "myOtherStack"
> go stack "myOtherStack"
> set the fileName of player "PlayerThumbnail" of "myOtherStack"
> to theMovieFilePathName
>
> One other thought, remove the parentheses in
> "go stack the (short name of me)"
> Rev may see that as: go stack the "myOtherStack"
The stack stored in myCallingStack is the stack that called this
function. I have checked this, anyway myCallingStack is not used
until after the crash.
The stack referred to as "me" is the library stack, e.g. the same
stack that the above code is executing in. It is intially loaded
using "start using", then when a particular function is called. I
want the stack to be displayed and to become the top most window. The
keyword "me" *always* refers to the object that the current script is
executing in.
Any other ideas?
All the Best
Dave
More information about the use-livecode
mailing list