I got temporarily burned by something similar to this. I had a public
property in a custom component which really should have been private.
But when I changed it to private, I got a run-time error when the
custom component was constructed. It turned out to be an issue with
the SetProperty transition that was changing the value of that
property as part of a state transition. It had the attribute
target="{this}", and when I took that out, it worked like a charm
even though the property was private. Apparently <SetProperty
target="{this}".../> works on a different scope than <SetProperty .../
> (without any target).
--- In [email protected], "Glenn Williams" <[EMAIL PROTECTED]> wrote:
>
> Ok,
>
> So I worked out what I was doing wrong.
>
> As my custom component was not in fact based on the original Panel
> class, but a custom panel (lets call it myPanel, in the name space
> 'lion'), the custom component being started like this:
>
> So I was not in fact having the original problem, and you as I first
> assumed you can in fact use target="{this}" to point to the class
that
> hold the states you wish to transition
>
