[FreeNX-kNX] Does freenx inherit client window behavior?

[Les Mikesell]

Terje Andersen wrote:
> 
> When switching to another client, and even more important, to another  
> OS/other X11 server, you might end up changing the geometry, and/or  
> X11 extensions, which then will be used in the session being resumed.  
> This can both result in not being able to resume, or some "quirks"  
> might appear (like those you describe).
> 
> Take a look at the following information from NoMachine:
> http://www.nomachine.com/ar/view.php?ar_id=AR03C00166
> 
> At this page (http://www.nomachine.com/fr/view.php?id=FR02E01636) you  
> find that NoMachine has plans for fixing these issues:
> 
> "In the current implementation, when the agent initializes its own  
> screen it inherits some parameters and structures from the target  
> display, e.g.: depth, visuals, pixmap formats, picture formats."
> 
> This page also gives some nice background info:
> http://www.nomachine.com/ar/view.php?ar_id=AR02F00506

Thanks - it hasn't been a serious problem but it just seemed strange 
that the windows would sometimes retain the wrong behavior for the 
connected client after switching.

> At the current implementation in the !M NXClient, you can't resize the  
> client display (Like on X11 clients; Max/Linux/etc.) - the client will  
> resize the client display on session resume, you can't do it yourself.
> 
> more info regarding this and Mac clients:
> http://www.nomachine.com/tr/view.php?id=TR06E01730
> http://www.nomachine.com/fr/view.php?id=FR11C01172

I never request a full-screen window so I hadn't run into that problem 
directly, but I have been trying to connect to a shadow session on a 
linux console and while the Mac client connects, it opens a wrong-sized 
window (perhaps the bug above) and windows clients haven't been able to 
connect at all (perhaps the render extension or something about the X 
session can't be matched).

-- 
   Les Mikesell
    lesmikesell at gmail.com