2014-07-02 1:55 GMT+03:00 Bill Spitzak <[email protected]>: > > > On 07/01/2014 12:35 PM, Jasper St. Pierre wrote: >> >> "A blink in the highlighting"? > > > Yes. Say the client wants to highlight the button being pressed and it has > popped up a menu, If the mouse is moved from the button to the menu, the > client wants to keep the button highlighted. > > If in fact the server sends an "exit" event and then an "enter" event for > the menu, a naive client will draw the button un-highlighted (since as far > as it knows the exit was because the mouse entered a different client's > window) and then when it sees the enter it has to draw it again highlighted. > If it does a commit, the user will see it blink. This is wrong.
If the client hasn't received a "popup_done" event it knows the popup is open and has the focus, so it knows it should keep the button highlighted in your example. Not sure if you have other examples, I can't think of any where having enter/exit events is a problem. -- Giulio > > Now obviously the client can wait (I think actually zero time because it > should be in the same block of events) and see if there is an enter event, > but it would be a lot easier on the logic if it did not get the enter event > at all! > > This is not a joke, these sort of problems make toolkits annoying and > complex to write. > > _______________________________________________ > wayland-devel mailing list > [email protected] > http://lists.freedesktop.org/mailman/listinfo/wayland-devel _______________________________________________ wayland-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/wayland-devel
