You need to sink the event type (Event.ONCLICK) to the Composite widget's element. Imagine how "fast" you app would be if onBrowserEvent was called on any event like mouse move.
On Sep 11, 1:31 am, "Gerwood Stewart" <[EMAIL PROTECTED]> wrote: > Do composite widgets like excepting click events? > > I've tried making a basic composite widget with a HorizontalPanel as the > initWidget. I've added SourceClickEvents and created the functions and > overriden onBrowserEvent. > > It appears onBrowserEvent is never getting triggered. > > Is there any basic reason for this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
