I definitely don't agree ... you're too developer centric ... This MagicPixel thing *IN TCE MODE* is troubling for users and your workaround is NOT a good option because the desktop is minimized then, thanks to a little daemon running, maximized again which is extremely confusing and frustrating for users. In TCE mode, there is no need for such thing and there MUST be a way to disabling it completely. This is what has been done by a server side switch which is fine for most *TCE* cases, now, I can understand that it can be desirable to keep that stuff for some other use cases but then, don't do tricks like that, just keep it and inform your users OR add the ability to disable this behaviour client side if disabling it server side really bothers you.
Regards, Walid Moghrabi
TRAVAUX.COM BAT I - PARC CEZANNE 2 290 AVENUE GALILEE - CS 80403 13591 AIX EN PROVENCE CEDEX 3
----- Mail original -----
De: "Stefan Baur" <X2Go-ML-1@baur-itcs.de> À: x2go-dev@lists.x2go.org Envoyé: Vendredi 18 Mai 2018 00:49:29 Objet: Re: [X2Go-Dev] Different behavior of X2Go Client from Desktop and TCE
Am 18.05.2018 um 00:39 schrieb Nable:
On Fri, May 18, 2018 at 1:18 AM, Stefan Baur <X2Go-ML-1@baur-itcs.de <mailto:X2Go-ML-1@baur-itcs.de>> wrote:
[...] The problem arises on systems that have a Window Manager (like OpenBox), but no task bar, so no way to un-minimize the X2Go/NX-window once the user hits the magic pixel.
Are you sure that task bar is required? AFAIK any tool with window switching ability (e.g. bbkeys, xdotool, some custom quick-and-dirty libwnck script) would work, wouldn't it?
Well, we are using xdotool in one of our workarounds. But, in a ThinClient environment, such a workaround must either function automatically (detect minimize and un-minimize instantly), or give the user some visual indication that X2GoClient hasn't crashed, but just needs to be un-minimized. The way to do this, because even an only marginally trained user would still understand this, is showing a task bar with an X2Go icon. Otherwise, all the user sees is a completely blue screen once they hit the magic pixel. An advanced user might try key combinations like Alt+Tab, but I wouldn't be sure that they help restoring the window to fullscreen.
Oh, and as stated above, we tried xdotool for a workaround, but sadly, it's not as simple as it seems and can trigger some nasty side-effects. That's why we went for the other workaround - disabling OpenBox as soon as the NX window spawns, then restarting it afterwards, once it has been closed.
Kind Regards, Stefan Baur
-- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243
x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you