Two servers One virtual desktop

Davide Baldini · Post by **Davide Baldini** » Sun Jun 12, 2011 7:23 pm

Can two wineserver share the same virtualdesktop?

I got nearly to an impasse: one windows application (A) must run
continuously without interruption, while (B) is supposed to respawn
frequently and interact with (A).

Well, whatever (A) application is has absolutely no influence on
troubles, but if (B) is autoHotKey (..yes i need that stuff under
debian) it's execution times get delayed increasingly at each run while
(A) stands in the same wineserver, no matter if i keep autoHotKey
closed for any while, until i quit both (A) (B) and conseguently wine.

If the respawning app is anyting else but autoHotKey, run times are
constant over executions.

I made many hour-long tests, the best of which are in alledged graph
(see note [1] ).

In my scripts i could work around this by assigning some windowing jobs
to a GNU program, and taking autoHotKey to a separate winserver from
(A) to handle only those operations which don't require windowing APIs
(wich seems to be possible only on shared winserver), but an all-wine
solution would be much more functional.

Idea?

[1]: alledged graph: runtimes (milli seconds) over number of executions
divided by 10.
Application (A) is generic; blue spots are autoHotKeys, red spots
are boxcutter.exe (for screenshot; generic app).
-------------- next part --------------
A non-text attachment was scrubbed...
Name: runtimes_over_executions.png
Type: image/png
Size: 21768 bytes
Desc: not available
URL: <http://www.winehq.org/pipermail/wine-us ... chment.png>

Davide Baldini · Post by **Davide Baldini** » Mon Jun 13, 2011 7:40 am

I think autoHotKey leaves some session-long alterations to wine status
when it quits, somehow slowing its own further executions.
A check with taskmgr.exe shows autoHotKey quits properly with no
processes hanged up.

I have absolutely no idea of what it keeps from tidying up.
How can processes alterations be tracked?

Thunderbird · Post by **Thunderbird** » Mon Jun 13, 2011 1:01 pm

Each wineserver instance is equivalent to a standalone windows instance. (wineserver is Wine's equivalent of the Windows kernel) Both really can't share the same wine desktop. If you really need something like autohotkey, use a linux equivalent of it. There are tons of tools to script keypresses / mouse movement on Linux.

Davide Baldini · Post by **Davide Baldini** » Fri Jun 17, 2011 5:57 am

On 06/13/11 20:01, Thunderbird wrote:

Each wineserver instance is equivalent to a standalone windows instance. (wineserver is Wine's equivalent of the Windows kernel) Both really can't share the same wine desktop. If you really need something like autohotkey, use a linux equivalent of it. There are tons of tools to script keypresses / mouse movement on Linux.

I managed it my way avoiding the need to respawn autoHotkey by a FIFO
that feeds commands to the same always-on-run istance ...
I already wrote the scripts; too bad I deep-tested them late.