[FreeNX-kNX] Obtaining the X Windows ID of the NX window

[Terje Andersen]

   ----- Melding fra brendan0powers at gmail.com ---------
    Dato: Wed, 3 Oct 2007 20:03:31 -0400
     Fra: brendan powers <brendan0powers at gmail.com>
Svar-til: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>
    Emne: Re: [FreeNX-kNX] Obtaining the X Windows ID of the NX window
     Til: User Support for FreeNX Server and kNX Client <freenx-knx at kde.org>

> Do you know if the cygwin x server is running in rootless mode?
>

   The Cygwin X-server (cygserver.exe) is run as a "service" - it's  
not registered as a windows-service, but during the connection the  
NXClient checks for this program/service and will, if necessary, start  
it. When the connection is terminated/suspended, the X-server will  
still be running in memory awaiting next connection.

   Since this program is run in the background, it has no window itself.

> On 10/3/07, Terje Andersen <terander at guard.zapto.org> wrote:
>> On Wed, 2007-10-03 at 14:35 +0100, Seb James wrote:
>> > On Sat, 2007-09-29 at 22:19 +0100, George Wright wrote:
>> > > On Wednesday 26 September 2007 09:29:30 Seb James wrote:
>> > > > > > NX> 999 X Window ID:2341
>> > > > >
>> > > > > Don't like it.
>> > > > >
>> > > > > Better use a NX 728> X Window ID:2341, but I don't know if   
>> its already
>> > > > > available at that moment.
>> > > >
>> > > > Fine - I actually put 999 in there to say "some number which   
>> would make
>> > > > sense within the NX numbering scheme".
>> > >
>> > > Is there any reason why this should be X Windows specific?   
>> Ideally we'd want a
>> > > cross-platform Window ID to be reported back, unless there's  
>> no  possible use
>> > > case for the Window ID on !X11.
>> >
>> > I don't see why it shouldn't be just "Window ID" to be interpreted in
>> > the most suitable way for the OS, whether or not the client is running
>> > X, Windows, a pure framebuffer, or whatever.
>> >
>> > However, the nxagent is always running on the NX server machine, which
>> > currently has to be X. I think that whatever the client is running on,
>> > the nxagent will think that it is creating an X window and will have an
>> > internal variable holding that X window ID.
>> >
>> > I don't know how NoMachine's Windows client works - does it run up a
>> > pseudo X server in Windows?
>> >
>>
>> The Windows client uses a Cygwin X-server that the applications from the
>> nxserver is shown on.
>>
>>
>> ________________________________________________________________
>>       Were you helped on this list with your FreeNX problem?
>>      Then please write up the solution in the FreeNX Wiki/FAQ:
>>    http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>>           Don't forget to check the NX Knowledge Base:
>>                   http://www.nomachine.com/kb/
>>
>> ________________________________________________________________
>>         FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>>        https://mail.kde.org/mailman/listinfo/freenx-knx
>> ________________________________________________________________
>>
> ________________________________________________________________
>       Were you helped on this list with your FreeNX problem?
>      Then please write up the solution in the FreeNX Wiki/FAQ:
>    http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ
>           Don't forget to check the NX Knowledge Base:
>                   http://www.nomachine.com/kb/
>
> ________________________________________________________________
>         FreeNX-kNX mailing list --- FreeNX-kNX at kde.org
>        https://mail.kde.org/mailman/listinfo/freenx-knx
> ________________________________________________________________
>
>

----- Slutt på melding fra brendan0powers at gmail.com -----


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/freenx-knx/attachments/20071004/663c920d/attachment.html>