On Wednesday 20 June 2007 00:38:32 P T Withington wrote: > Cool bug! Please file at (http://jira.openlaszlo.org). Done, as: http://jira.openlaszlo.org/jira/browse/LPP-4172
> I would consider this a bug. Surely if you override an attribute
> with a method in a subclass, you should also override any setter
> associated with the attribute?
It makes sense to me :)
> As a work-around, you could add the following method to your test class:
>
> <method name="setPlay" args="value">
> this.addProperty('play', value);
> </method>
Thanks, will give this a go.
> This will override the setter in your superclass and correctly
> install your play method. Of course, that will mean your subclass
> will not obey the normal play protocol of views.
No matter in this case, it just relays the play signal to another object.
However, there's an interesting point raised here (academically, anyway, I
don't need to do this), the implication from what you say is that the normal
behaviour for 'stop' will be invoked even if it is overridden. Is this the
case? I kinda assumed that JS would use a Java-like method, such as
super.method(), to do this, but it's never come up for me.
--
Robin <[EMAIL PROTECTED]> JabberID: <[EMAIL PROTECTED]>
Hostes alienigeni me abduxerunt. Qui annus est?
PGP Key 0xA99CEB6D = 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D
pgpm6OqGccwaw.pgp
Description: PGP signature
