Printable View
The issue is that whatever toon has focus on my secondary machine, will not receive movement broadcasts from the server. This only happens when I use my USB XKeys (which makes it even more odd). If I force another window on top, it will receive the movement broadcast. Any thoughts, or am I just SOL? Note, this is when I use the ARROW key commands (<UP> <Down> etc.)
Does it happen with 1.3.2?
yes I use a different API call to do the foreground window, so it's more compatible with DirectInput, and so the shift key capitalises.
so it does make sense, im not sure if your saying it broke in 1.3.3 but i highly doubt it.
and its probably limited to these keys right? so you could map it to a different key - at some point I might buy one of these, but right now i'm unemployed!!
/* char extendedCodes[] = { 13, // NUM ENTER
163/, // RCTRL
111, // NUM SLASH
161, // RSHIFT
44, // PRINTSCR
165, // RALT
144, // NUMLOCK
36, // HOME
38, // UP
33, // PGUP
37, // LEFT
39, // RIGHT
35, // END
40, // DOWN
34, // PGDN
45, // INS
46, // DELETE
91 }; // LWIN */
True, I am not sure it broke in 1.3.3 ... I jumped a couple versions (and stopped using KeyClone for anything but launching) somewhere in there. Are you saying to map Down -> Down etc?
no on your x-keys use non extended keys (ie the ones i didnt list).
mapping within my software may fix it but i may choose to use scan codes again for mapping at some point, breaking the solution
basically, i dont want the answer to x-keys to be "map certain keys to self and switch on the option to use virtual keys", so its unsupported until i buy one!
Skarlot,
I understand. I was leaning towards that fix myself, but I was/am reluctant because of the effort involved :thumbdown: I use the 128 Key and have 4 different classes in my setup ... which means I am at a premium for "key space" - not in terms of the keys themselves, but in terms of the open bindings available.
In all, I'd say I am rather disappointed with the XKeys - if I use the extended keys (like "Up") on my G11 all of my toons move just fine. In fact, I have been using that as a work-around. What is different between the signal the XKeys is sending vs that sent by the G11? My personal thoughts are that the G11 may have the correct DInput drivers, while the XKeys does not.
how am i to know that then! i dont have either. and im hardly likely to search there software packages without the hardware :P + if i knew, id just code it. its not all that complicated and im confused how there is a problem at all. i'll let it whirl around my head and maybe put a debug option on or something, i dunno. last time i did a debugged build the person didnt bother to respond! you could always write a simple keyboard hook to see how the xkeys is reporting, if so able/willing :P
Why not switch that to Octo too? I just discovered it and it works perfectly.Quote:
Originally Posted by 'Ghallo',index.php?page=Thread&postID=82079#post82 079