Indeed. But how about this: the client sends the compositor a hint stating its maximum unresponsiveness interval, and sends keep-alive messages when idle. If the app doesn't respond in time, and the user tries to interact with it, the compositor can offer to kill it (or something).
Mak On Fri, May 13, 2011 at 11:26 AM, Daniel Stone <dan...@fooishbar.org> wrote: > On Thu, May 12, 2011 at 06:22:01PM +0200, Michal Suchanek wrote: >> You can't expect that every single client is high-priority and lag-free. > > Run better clients, then? Or stop trying to micro-optimise for the case > of pressing the close button on an unresponsive client? > > Cheers, > Daniel, who wants the bikeshed to be violet > _______________________________________________ > wayland-devel mailing list > wayland-devel@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/wayland-devel > _______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
