Extended mouse keys... having some trouble.

[seanwcom]

Hey everyone, I hope this hasn't been covered already - I did some searching, but it's late...

I have a Logitech MX1000 - lots of buttons on it. Over the years, I've become accustomed to having all sorts of keybinds set to the miscellaneous buttons. It may help to take a look at the mouse to follow along. Here's a picture.

As you can see, there are buttons on the left side as well as buttons around the mouse wheel. That button around the mouse wheel is essentially a 4-way pad for me. The wheel rocks left and right, and the buttons in front and behind the wheel complete the 4-way with up and down.

So, moving on... what I've done in the past is use the Logitech software to hard code some funky bindings to those buttons (ctrl-alt-/ for example). Then it was as simple as binding that to the appropriate button on my action bars. So now, with Innerspace/ISBoxer, I'm trying to just recreate that, but send to two active wow sessions at once. Nothing special, no round robins, just send the one key press to both windows.

I know it sounds simple, but for the life of me, I can't get it to work. I've watched every YouTube video I can find, I've got all sorts of other Key Maps working just fine, even a round robin Hunter's Mark... I think I have a good idea of how everything works. But I can't get the mouse buttons to pass thru...

Right now, I have made things simple. I created a Key Map called 'Mouse Square.' Within that Key Map, I have a mapped key called "Wheel Rocker Forward" that is bound to Ctrl-Shift-[. I've created a 1 step WoW Macro Action, that just does /cast Arcane Shot - and I have it bound to Ctrl-Shift-Alt-Up

I head in game and without even trying the mouse, I press Ctrl-Shift-[ - and nothing happens. I don't get a 'no target' error, or if I have a target, I still get nothing. My other key maps are working (follow, assist, etc). Oh, and I have my Character set in the key maps as well...

Anyway - not sure what's going on here. I'm sure I've messed up something along the way, I just don't know what. I've attached my xml file - could someone help me out? Also, let me know if there's anything else I need to post up...

EDIT: oops, the XML file was 5k too big. I've zipped it, and also put it up on my website if you don't want to download a zip. (http://www.seanw.com/ISBoxerToolkitProfile.XML)

Thanks all!

[seanwcom]

More troubleshooting this morning... still no luck. But it appears that Innerspace just isn't receiving mouse button information.

I've simplified things even more now. I've gone through the Logitech software and bound the buttons to F13 through F20. In IS Boxer, those correspond to key maps that create in game hotkeys. Rather than create WoW macros, I have it set to just pass a simple keystroke action to all characters.

I can go in game and press the keystroke hotkey (in this case, CTRL-Up) and both characters do the action - that's a good step forward. But the darn mouse buttons just aren't working... anyone have any ideas why Innerspace isn't picking them up?

Thanks all...

[aboron]

I used the logitech software to make my mouse buttons send keystrokes to innerspace, but I had to run the mouse software as admin for it to work properly.
Since running a startup application as admin is a pain and complains about running it until i manually approve it, I created an "on startup" schedule event to run it as admin, which didn't complain or ask me to approve anything.


Then i changed mice to a saitek and their software can map the buttons in a way that IS picks them up without me doing anything funky to run their software.

[Lax]

The extra buttons you're mentioning are non-standard, and Logitech doesn't make it easy

Aboron's suggestion is right: If you're using Vista or Windows 7, Inner Space has to be run as Administrator, and therefore the game will also be running as Administrator. This means that applications that are supposed to interact with the game must also be run as Administrator in order to emulate or detect keystrokes. Ventrilo for example may not be able to detect your Push to Talk key unless it is running as Administrator, because the elevated level of the game will otherwise prevent it. Similar Logitech's software can't emulate the keystrokes the way it does, because of the elevated level of the game. More information on using unsupported Logitech devices: http://www.lavishsoft.com/forum/viewtopic.php?t=4109

[seanwcom]

*FOREHEAD SLAP*

Of course... *sigh* I wish I had thought of that! hehe... I'm running W7, so of course I've got everything running as Administrator, but I didn't even think of the Logitech software running in context of the normal user, therefore having no access to admin processes.

Thanks guys!