Lax wrote:
> 1. WinEQ 2 was built for a few specific games, one at a time. This means that the input handling system is tailored to each game. EverQuest changed its mouse system some time after the client version you wish to use, and unfortunately as it was a one or the other choice, only the current version of EverQuest is supported by WinEQ 2. One of the best things about Inner Space is that it is game-agnostic, and the input handling system is designed to work for any and all games, so it should of course work for both the old EQ client, and the new EQ client.
yeah - WinEQ2 mouse actually works well - what does not work with an old
client is the keys - no keypress is doing anything
> 3. If you're using Inner Space, you do not need to use Keyclone, as you may have already discovered hints of as you've played with GlobalBind. The following thread on the Lavish forums (you will need to log into the site or following the link will tell you the topic does not exist) was started by someone who was trying to do exactly what you're looking for, and contains lots of helpful information from myself and others: http://www.lavishsoft.com/forum/viewtopic.php?t=3712
>
i did indeed read that topic already and got what i wanted to work -
the Issue was that EQ Game settings needs to be force foreground or it
will not work
However are you aware that alt+ctrl+1 etc does not work for eq in
innerspace to change between windows ? i have to alt tab manually - it
only works as long as you havent loged in (because that isnt directx i
think just some visual basic gui)
> 4. I realize the process you're taking to get this stuff working is not particularly easy to follow and understand, and there is certainly not an obvious path laid before you without knowing exactly where to look. I am in the process of building the next generation of WinEQ 2, using the as yet unreleased Inner Space 2 engine. This will include a very easy to use system to allow you to send keystrokes to other windows, even on other PCs if you wish, as well as a host of other new and useful features. The beta should be available within a month or two, so keep an eye out for that. Another top priority for Inner Space 2 and the next generation of WinEQ is to drastically improve the quality of the documentation, so as to avoid any misgivings over what GlobalBind does, etc

>
No problem, im a programmer myself so it wasnt that hard to follow -
however i still have one issue with the bind method.
I cannot seem to map the same key to trigger an action which should
execute on another window
i.e. lets say i press w in window1 and it should execute w in window 2 -
nothing happends
however if i lets say bind an unused key to execute the window2 w key -
everything works
This is not realted to specific actions - it seems to apply for all
example :
bind -press left "left" relay is2 press -hold "left"
bind -release left "left" relay is2 press -release "left"
should allow me to walk left if i had bound that key to move left on the
other node - but it doesnt work
however
bind -press left "left" relay is2 press -hold "a"
bind -release left "left" relay is2 press -release "a"
works fine - since a is an alternative key press to walk left
More confusing:
i bound attack to the q key - now when i press q i want to transmit it
to all instances
bind q "q" relay all press "q"
what happends is - that q is executed 2 times on the first window - i.e.
it gets turned on and off in the same second
(i even believe when you do this a kind of endless loop should happend
because when you say press q on the window1 it should execute the action
which was bound to the q key - which executes itself again =)
so my workaround for this was to just trigger an alternative key
bind q "q" relay all press "0"
because i also bound attack to 0 - this way it works - very confusing
Can you shed any light into this.
Thanks and great programm =)