On Tue, Jul 31, 2012 at 3:00 PM, Pekka Paalanen <ppaala...@gmail.com> wrote: > Which (non-existing) code are you referring to? > > The unresponsive busy cursor thing is triggered in the desktop-shell > plugin, and the actual busy cursor is set in the desktop-shell client. > It does not require any setup from the client that becomes > unresponsive. Or that is how it is supposed to work. > > You were using Weston, and desktop-shell client is working, right?
Sorry, what I meant is: When the client doesn't set any pointer surfaces as it's supposed to, you get the last active cursor when entering the window (like the textedit cursor when hovering from a terminal to the client's window). That was the case with the SDL driver when I started working on it. Since the pointer didn't indicate anything useful, I assume I also ignored the busy cursor trying to tell me about the clients non-responsiveness. And I just rechecked, and without the pong response the cursor switches to the busy state after a short while, so everything works as expected. It was just me ignoring the signs :) Thanks, Andre _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel