Page 1 of 1

more than one window

Posted: Sun Oct 21, 2018 9:32 pm
by Yekun
I play a game called Lineage2 and use x-mouse normally. The game runs in window, and I keep 4 or 5 windows of this game open at the same time, but the x-mou runs in only one window at a time. Is there any configuration that allows me to run the x-mouse with different commands and simultaneously in each separate and minimized "vitual mouse" window of my game? If not, is it possible to add this in new versions? thanks allot

Re: more than one window

Posted: Sun Oct 21, 2018 9:52 pm
by phil
Sorry, I don't really understand the questions.

I presume you are talking about sending actions.keystrokes to the game window? In terms of simulated keystrokes, XMBC works with the active window - the one that has keyboard focus. That is because when sending simulated keys, they are stuffed into the keyboard input buffer - so they go to whatever window has keyboard focus. XMBC cant do anything about that, other than changing focus by activating the window under the cursor (which you can do by adding a {LMB} ot {ACTIVATE} tag before your keys.

So no, there is not a lot that I can do in this area in future versions that is not already available. But you might get some mileage with the {activate} tags to activate the window so that it has keyboard focus before sending any actions???

Thanks,
Phil

Re: more than one window

Posted: Mon Oct 22, 2018 3:54 pm
by Yekun
Thanks for your response.
I need commands in the open window (today it works normally) and also in the minimized window simultaneously even if it is necessary, perhaps, to open two x-mouse, or emulate some "virtual mouse".
I will wait for new versions, thanks

Re: more than one window

Posted: Mon Oct 22, 2018 4:23 pm
by phil
I'm sorry to disappoint but that is not possible. You can wait for new versions for as long as you want, but I simply cant do it so no new version will be able to do it.

XMBC uses Micrsoft's SendInput API to send keystrokes etc. This API stuffs data into the Windows keyboard buffer. Windows then distributes that buffer TO THE ACTIVE window ONLY. If you had two xmbc open (even if that were possible which is isn't as XMBC is global anyway) it wouldn't matter, because they still would both only be able to send input to the same buffer in Windows. Windows does not allow you to send simulated input to anything BUT the active window using Microsoft's SendInput API (which is the only reliable way of sending input).