[X2go-Dev] core dev-team testing x2goclient during next week

[John A. Sullivan III]

Hi, Alex. Thanks again for taking this seriously. I'll respond in the
text - John

On Thu, 2011-07-28 at 08:46 +0200, Oleksandr Shneyder wrote: 
> Am 27.07.2011 18:44, schrieb John A. Sullivan III:
> 
> > Hi, Alex.  Although the packing and multi-session problems have
> > mysteriously vaporized as I reported elsewhere, I can confirm that we
> > still have the following:
> > 
> > 1) Full screen toggles do not work in Windows - no magic pixel,
> > AltCtl-M, AltCtl-F.
> > 
> > 2) AltTab does not work as expected in Full Screen mode - in fact,
> > rather than scroll through the X2Go desktop applications, it is
> > currently the only way to break out of full screen!
> 
> 1 and 2 are xvcsrv issues. As I can remember, It was your idea to start
> X in full screen mode by full screen X2Go session. The magic pixel and
> AltCtl-M, AltCtl-F are possible to use only with window manager (on
> windows only if vcxsrv started in rootless mode). The only way to do
> this with vcxsrv in full screen mode is find a WID of vcxsrv and send
> WS_MINIMIZE to it main window. To make it possible we should modify both
> - x2goagent and x2goclient. My opinion - it is wrong idea. Vcxsrv should
> be started in rootless mode even for full screen X2Go sessions. If it is
> not working correctly, we should communicate with developers of vcxsrv
> to solve this issue.

That makes sense except, if I remember correctly, there is a difference
between full screen and rootless.  If I choose fullscreen, it truly is
full screen and the user perceives only one desktop.  It is as if their
X2Go desktop is their only desktop and they do not have the problem of
frequently closing their desktop accidentally when closing a maximized
application, i.e., clicking on the wrong "x" in the top corner.  This
setting is highly desirable for those who work only or primarily in
their X2Go desktops (the majority of our clients).

In rootless, the X2Go desktop is still placed within a Windows but it
takes the entire available area aside from the window decorations.  This
is highly desirable for those who frequently toggle between their
physical and x2go desktops.

I would think we would want to accommodate both (and more!) styles of
work.  When in full screen mode, my desire would be that the keystrokes
would work as if the x2go desktop was the only desktop, i.e., Alt Tab
cycles through the x2go desktop apps.

> The same is with alt+tab. This events should catch vcxsrv. You can
> specify by x2goclient the X-server you want to use and the command line
> arguments to starting it. As far as you find a best combination of
> vcxsrv version and command line arguments I'll make it default.
> 
> > 3) I get a knotify: no process found error when exiting the Windows
> > session.
> 
> old workaround for kde3, I'll take care about it.
> 
> > 4) Evolution selection (as a representative graphics issue) is still
> > painfully slow
> 
> Still can not reproduce it. But even if I can, it is a nxlib problem and
> will be not easy to solve. All output of nxlibs you can find on client
> and server side in ~/.x2go folder. Have you this problem only with
> recent versions of nx or was it always present? If it is a new problem,
> please find a last version of nxlibs without this problem, it can help
> to find a bug by researching of changelogs and diffs.


I'll have a look and try to dig deeper. It is a Windows only problem (or
perhaps I should say Windows exacerbated).

As I mentioned earlier, I do have a concern that a number of these
issues may not be specifically X2Go but rather vcxsrv or NX.  The vcxsrv
dev has been fabulously supportive.  I don't know about NX or if we have
the capability to fix it ourselves.  Thanks again - John
<snip>