| |||||||||||||
LFCS 2012: X and WaylandLFCS 2012: X and WaylandPosted Apr 13, 2012 8:28 UTC (Fri) by khim (subscriber, #9252)In reply to: LFCS 2012: X and Wayland by drag Parent article: LFCS 2012: X and Wayland Windows solves this problem with timeouts. Program can draw it's own decorations and process events in any way it wants to do that, but if it does not respond in timely fashion then OS imposes standard borders and allows you to do standard things (move/resize, close, etc).
(Log in to post comments)
LFCS 2012: X and Wayland Posted Apr 13, 2012 9:25 UTC (Fri) by dgm (subscriber, #49227) [Link]
This cannot apply to Wayland, because there's no concept of "draw your decorations" message. All drawing is application's business in Wayland, and done in a single step.
LFCS 2012: X and Wayland Posted Apr 13, 2012 9:34 UTC (Fri) by khim (subscriber, #9252) [Link] So what? Window manager can easily put it's own window with just a decorations and empty transparent body which will give the same affect.
LFCS 2012: X and Wayland Posted Apr 16, 2012 13:38 UTC (Mon) by dgm (subscriber, #49227) [Link]
Putting some standard borders is trivial, yes. The problem is detecting that the application is not drawing it's decorations, or more exactly, that it's not doing it so because it's hung or something (because it could be a feature, you know...)
A good alternative is let users point hung up applications themselves (using something like Xkill) and draw the "standard frame" then.
|
|||||||||||||