On Mon, 27 Sep 2010 17:01:24 +0300 Timo Juhani Lindfors <[email protected]> said:
> Carsten Haitzler (The Rasterman) <[email protected]> writes: > > 1. if user client does an xgrab(server/keyboard/pointer) and u stop socat > > before the grab is released.. you're SOL. a "race condition" or more a > > "state condition" you havent accounted for. > > A possible solution is to just revert to the old "switch to another > virtual console" approach or sound an alarm through the speakers in > such a case. ugh! horrible usability. one should not rely on vt switching as a usability feature - if you need this to fix/get around something, it's a bug and it needs fixing :) > > 2. user clients like the wm and cm will cease to work here while you have > > the root stopping socat - this will effectively bring the display to a > > grinding halt. much like #1. > > The xterm spawned by root can still be used. It is ok in my use case > that it is not possible to move/resize this SAK "menu". it can only be used *IF* it happens to have been focused by the wm at that time... and you forget the cm. output updates can't be seen at all as long as its suspended. :) so the screen entirely will freeze (except for mouse cursor moving around) > > segment content and hat is just pixel data - so at worst they can spew out > > garbage pixels. not too different to what many clients do anyway :) so this > > is harmless. > > Good to know. > -- ------------- Codito, ergo sum - "I code, therefore I am" -------------- The Rasterman (Carsten Haitzler) [email protected] _______________________________________________ [email protected]: X.Org support Archives: http://lists.freedesktop.org/archives/xorg Info: http://lists.freedesktop.org/mailman/listinfo/xorg Your subscription address: [email protected]
