You can use a single Stack<HandlerManager> for all your events for one
Widget, or in a more static context if you can control where all your
widgets send all their Handlers.
In the old model, you needed a collection for every type of listener, and
{this is BIG} you couldn't call
widgetInst.removeListener(ClickListener.this}. It gives concurrent
modification exception because the Listener is being iterated over when it
is called, and the java-proper nature of GWT collections doesn't allow
concurrent modifications.
HandlerManager is a seperate object than the actual Handler, and it removes
this psuedo-synchronization issue.
--
"He whose desires are drawn toward knowledge in every form will be absorbed
in the pleasures of the soul, and will hardly feel bodily pleasure --I mean,
if he be a true philosopher and not a sham one." - Plato
"Wise Words Woven With Will Wakes Worlds" - Alyxandor Artistocles
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To post to this group, send email to Google-Web-Toolkit@googlegroups.com
To unsubscribe from this group, send email to
google-web-toolkit+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---
