DomEvent-s have their types lazily created, because they're registered in a global, er, registry, to easily match event types (from the browser, evt.type, i.e. a string such as "click", "mouseover", etc.) to DomEvent.Type instances. Most other events don't need this, but some of them could benefit from it: some events have a static fire() helper method; when invoked, if the TYPE private field hasn't been initialized, it means getType() hasn't been called, i.e. no handler has been registered for the event, so the fire() help method can exit early, without event creating an event instance and calling the event bus.
-- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/yiNrbRh9FwIJ. 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.
