ian, thanks for responding. i really meant, "how, once DOM.setCapture() has been called, does the *implementation* of GWT ensure that that actually does the job it's expected to do".
the issue i'm encountering in the python port (pyjamas) is that when the mouse "wanders outside" of the area represented by the caption element (the bar at the top), all bets are off. you'd better not let go of that mouse-down, because, if you do, then when you move the mouse _back_ into the caption area at the top of the dialog, the mouse-move events continue to get captured, but, of course, the dialog keeps moving away from your mouse!! really irritating. i've spent several months trying to track this one down. On Oct 16, 10:13 pm, "Ian Bambury" <[EMAIL PROTECTED]> wrote: > DOM.setCapture (element) - or something like that, or whatever has replaced > it - I haven't had to use if for ages - means that the element can be set to > 'own' all mouse events for a while. > Ian > > http://examples.roughian.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
