Paul TBBle Hampson Paul.Hampson@Pobox.com writes:
The three possibilities I see are:
*) Most recent foreground application catches XI2 events in its own spawned thread. Need to elect a replacement on process exit. Easiest to co-ordinate with non-XI2 hook-feeding code.
*) Wineserver gains an X11 connection, for XI2 use only. This is generally bad, only here for completeness.
*) A new process (ala services.exe) which grabs XI2 events from X11 via its own connection and feeds them to the wineserver.
It should run in the context of the explorer process, no need for a new process.