New to Innerspace. Copule of Q's.

j3ron · Post by **j3ron** » Thu Sep 08, 2005 1:54 am

So im going to be using IS for WoW.

I want to have 2 acc.'s running - one fullscreen (is1) and a heal-bot PiP (is2) that gets sent keystrokes from is1's numpad. I have the PiP working - the keys get sent but....

1: When running pip.iss from is1 it moves the is1 window so the top and left windowedges are just outside the screen. Is that something that can be switched off? To see those to sides of the window i have to drag-resize the window until i can see the top (statusbar) again and then move it down and to the right.

2: This one is pure lazyness. Is it possible to set IS up somehow so that when i have started is1 (with my keybinds in the Startup Sequence) and i startup is2 - that it then swithes back to is1 and runs pip.iss so i get is2 in PiP?

Ultimately i would love to be able to set it up so I start up one client and the rest of the setups get done from scripts (running PreInit on is1, starting client2, switching back to is1, running pip)

j3ron · Post by **j3ron** » Thu Sep 08, 2005 2:29 am

no edit button...

3. Why doesn't num5 (on the numpad) work when sending keypresses? Anyone have a clue? Also happens for a friend of mine. All the other buttons send the right keypress and it 's not the bind.

Post by **Lax** » Thu Sep 08, 2005 10:29 am

1. PIP.iss is a script, and really does nothing any other script couldnt do. If you want to move the window, you can set up the script how you like. The default settings for the PIP script right now are probably in DefaultStartup.iss, but they need to be removed. The PIP script needs to be replaced with something better and probably given a ui window to help you configure it.

2. Yes. In fact, you can just add it to your startup sequence if you always want PIP. You can also relay commands to other sessions, for example "uplink relay is1 run pip"

3. When you get an issue like this, report it as a bug. It irks me when people assume theyre doing something wrong that should probably work just fine. Here's the answer.... it IS actually sending the key. However, numpad 5 only does something if you have numlock on, and Inner Space is emulating the key as if numlock is off. If I bind numpad 5 to something in WoW, the only way it will accept the key is by having numlock on. Then the only way to use that binding is to have numlock on again. However, if I make an IS bind to "num 5", it only works if numlock is off!

I'll work on this.

Post by **Lax** » Thu Sep 08, 2005 6:35 pm

Build 2577, now available, specifically addresses this num 5 issue

j3ron · Post by **j3ron** » Fri Sep 09, 2005 6:05 am

Excellent. Thanks a bunch for the fast response.

Red · Post by **Red** » Thu Sep 15, 2005 8:53 am

[quote] It irks me when people assume theyre doing something wrong that should probably work just fine[/quote]

I would rather blame myself and then have you say "It's a bug, not your fault", rather than coming in here and saying "Lax, you broke my shit get it fixed!" and being wrong. :wink:

Yes, I'm trolling at work. :shock:

-Red

Post by **Lax** » Thu Sep 15, 2005 10:49 am

I would rather blame myself and then have you say "It's a bug, not your fault", rather than coming in here and saying "Lax, you broke my shit get it fixed!" and being wrong.

I would rather they dont attempt to place the blame, as any issue reported should be considered an investigation into a problem. If the problem is simply that they dont know about something, theyre doing something wrong, etc then maybe the solution is to explain things to them, and then fix the documentation, update information on the website, etc. If the problem is a bug, then the solution is obviously to fix the bug.

There's generally no reason for the user to place the blame, because they dont always know who to blame. The only one who can is the person with the answer