Yep, that makes sense - i was thinking that the parameter specified in the
annotation was a literal, but it's a prop so that will work nicely
Thanks guys
----- Original Message ----
From: Robert Zeigler <[EMAIL PROTECTED]>
To: Tapestry users <users@tapestry.apache.org>
Sent: Tuesday, 13 May, 2008 7:16:53 PM
Subject: Re: Changing a components property at runtime
Is "disabled" a parameter for the component?
If so, then why not make the dynamic "disabled" a property of the
parent component or page, and bind the component parameter to the
parent property?
For example:
the component:
@Parameter
boolean disabled;
...
The page or component that contains the component:
@Component(parameters={"disabled=disabled",...}
private SomeComponent comp;
@Property
@Persist
private boolean disabled;
public onActionFromSomewhere() {
return disabled=false;
}
On May 13, 2008, at 5/1312:58 PM , Toby Hobson wrote:
> This may sound like a simple question but I can't work out how to
> change a property programatically. Basically I'd like to disable a
> component from an event handler. I know I can pass params in via TML
> or using annotations but I can't find any setX() methods on the
> components
>
> Thanks
>
> Toby
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
