There is an enhancement request in Wicket JIRA for this issue, but it is
set to 1.5 release...http://issues.apache.org/jira/browse/WICKET-1525 In the meantime, the class I created merging AjaxSelfUpdatingTimerBehavior and AbstractAjaxTimerBehavior is working fine, although I agree that when the page refreshes on a timer it seems somewhat sluggish. hth, Daniel satar wrote: > > I know this is an old post but it hits an issue I currently have. I want > to provide the user the ability to turn on/off auto refresh of data from > the database. If all possible, I would like to use the original > AjaxSelfUpdatingTimerBehavior or at least the AbstractAjaxTimerBehavior > but it has the stopped boolean as a private with no way to set it back to > true and the methods that use it use it directly instead of calling a > method that I can override -- am I missing something? > > The man reason I want to do this is for performance trade-offs. I see that > if I set the timer off by calling the stop() method, the interface is much > snappier. It looks like another potential idea may be to override the > method renderHead, but I cannot override the respond method, which uses > the stopped boolean. > > Is there a better way to handle such a problem -- I am using Wicket > 1.4-r2. > -- View this message in context: http://www.nabble.com/AjaxSelfUpdatingTimerBehavior-and-ModalWindow-tp22202102p24595575.html Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
