Re: generalized way to ignore mouse input during screen refresh?
a nasty exception thrown, since the component clicked on no longer exists Is there a single, easy workaround for this? Obviously you can try to limit the situations where this occurs, like my redrawing as little as possible, or otherwise making things less time consuming, but it still seems like it would be good if there was a general mechanism for ignoring inputs once some kind of Ajaxy-process is started... - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://www.nabble.com/generalized-way-to-ignore-mouse-input-during-screen-refresh--tp21379945p21381260.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: generalized way to ignore mouse input during screen refresh?
On Fri, Jan 9, 2009 at 10:55 PM, Valentine2008 valentine...@alumni.sfu.ca wrote: I created a reusable component, PanelWithAjaxBusyIndicatingMask, which extends Panel. The functions it has: It will add a transparent mask layer to the current page to prevent further UI interactivity when there are any busy Ajax activities. The mask layer will have an animation gif and a configurable display text (the default is: Please wait…). Both the display text and the animation gif file are configurable in the constructors. I am proposing it to the Wicket developers. Hope they will incorporate it into the next release. It seems like the mechanism of blur that happens to background openign the modal window. Anyway, it would be great to share the code using wicket stuff, I think is a better way for some reason: component is immediately available, many people can use it to provide feedback and let the component grow, so eventually it can become a standard wicket component. getting commit accesso for wicket stuff is not complicated, I guess some project in wicket-stuff can host your component. -- Daniele Dellafiore http://blog.ildella.net/ - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: generalized way to ignore mouse input during screen refresh?
Yes. It is similar. But I didn't look at the source code of the ModalWindow. The idea I have put in https://issues.apache.org/jira/browse/WICKET-2017. - Valentine Daniele Dellafiore wrote: It seems like the mechanism of blur that happens to background openign the modal window. Anyway, it would be great to share the code using wicket stuff, I think is a better way for some reason: component is immediately available, many people can use it to provide feedback and let the component grow, so eventually it can become a standard wicket component. getting commit accesso for wicket stuff is not complicated, I guess some project in wicket-stuff can host your component. -- Daniele Dellafiore http://blog.ildella.net/ -- View this message in context: http://www.nabble.com/generalized-way-to-ignore-mouse-input-during-screen-refresh--tp21379945p21392474.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
generalized way to ignore mouse input during screen refresh?
So one problem we've seen in a few places occurs when a (somewhat slow) request happens that refreshes the page or component, but then the user clicks on a link on the pre-refresh screen, and ends up getting a nasty exception thrown, since the component clicked on no longer exists Is there a single, easy workaround for this? Obviously you can try to limit the situations where this occurs, like my redrawing as little as possible, or otherwise making things less time consuming, but it still seems like it would be good if there was a general mechanism for ignoring inputs once some kind of Ajaxy-process is started... - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: generalized way to ignore mouse input during screen refresh?
I created a reusable component, PanelWithAjaxBusyIndicatingMask, which extends Panel. The functions it has: It will add a transparent mask layer to the current page to prevent further UI interactivity when there are any busy Ajax activities. The mask layer will have an animation gif and a configurable display text (the default is: Please wait…). Both the display text and the animation gif file are configurable in the constructors. I am proposing it to the Wicket developers. Hope they will incorporate it into the next release. Kirk Israel-2 wrote: So one problem we've seen in a few places occurs when a (somewhat slow) request happens that refreshes the page or component, but then the user clicks on a link on the pre-refresh screen, and ends up getting a nasty exception thrown, since the component clicked on no longer exists Is there a single, easy workaround for this? Obviously you can try to limit the situations where this occurs, like my redrawing as little as possible, or otherwise making things less time consuming, but it still seems like it would be good if there was a general mechanism for ignoring inputs once some kind of Ajaxy-process is started... - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://www.nabble.com/generalized-way-to-ignore-mouse-input-during-screen-refresh--tp21379945p21381260.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
Re: generalized way to ignore mouse input during screen refresh?
Could you share the code, or at least the core idea of how it hooks into a normal page/component, in the meanwhile On Fri, Jan 9, 2009 at 4:55 PM, Valentine2008 valentine...@alumni.sfu.ca wrote: I created a reusable component, PanelWithAjaxBusyIndicatingMask, which extends Panel. The functions it has: It will add a transparent mask layer to the current page to prevent further UI interactivity when there are any busy Ajax activities. The mask layer will have an animation gif and a configurable display text (the default is: Please wait…). Both the display text and the animation gif file are configurable in the constructors. I am proposing it to the Wicket developers. Hope they will incorporate it into the next release. Kirk Israel-2 wrote: So one problem we've seen in a few places occurs when a (somewhat slow) request happens that refreshes the page or component, but then the user clicks on a link on the pre-refresh screen, and ends up getting a nasty exception thrown, since the component clicked on no longer exists Is there a single, easy workaround for this? Obviously you can try to limit the situations where this occurs, like my redrawing as little as possible, or otherwise making things less time consuming, but it still seems like it would be good if there was a general mechanism for ignoring inputs once some kind of Ajaxy-process is started... - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org -- View this message in context: http://www.nabble.com/generalized-way-to-ignore-mouse-input-during-screen-refresh--tp21379945p21381260.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org - To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
