[ISBoxer] Focus Follows Mouse Working?

Focus Follows Mouse Working?

I played around with ISBoxer again for a number of hours yesterday and think it has real possibilities for a 10-boxer (or anyone for that matter, just that organizing and structuring inputs is probably most important for those that have just tons of things going on).

Anyway, I love the idea that ISBoxer will use the Focus Follows Mouse philosophy, but I've checked that box and I still have to click in individual windows to get the focus there. Is anyone else having this problem? If it is broken for everyone I'll know not to mess with it anymore. If it is working for everyone else I'll know I'm missing something.

One other question - which type of changes in ISBoxer update real-time when you export updated code and which require a reboot of WoW or ISBoxer or even the computer? I *think* keymaps are supposed to update real time and that things like regions/layouts require a WoW restart, for example, but my experience hasn't confirmed this.

Thanks!

If you can copy/paste the window layout (right click on the window layout and select copy to clipboard, paste here it shows up as XML) I'd like to see why the focus follows mouse option doesn't work for you. I tested it in different ways before release and it worked wonderfully.

As of ISBoxer 36, Window Layouts now apply when you export; those required a restart in 35 or earlier. If you make changes to WoW Macros through ISBoxer, then you will need to /reloadui on the affected windows so the ISBoxer Addon (generated when you Export) can reapply the macros.

There's a few specific settings that might require a restart of the game, like if you change the IS console hotkey or the FPS indicator (2 settings in your Character Set) while playing. Nothing that you'd notice that I can think of though.

Lax,

Thanks for the help. Here it is:

<?xml version="1.0" encoding="utf-8"?>
<Box xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<ObjectType>System.Collections.Generic.List`1[ISBoxer_Toolkit.Configs.WindowSnapperProfile]</ObjectType>
<SerializedObject><?xml version="1.0" encoding="utf-8"?>
<ArrayOfWindowSnapperProfile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<WindowSnapperProfile>
<Name>Mag Kobalt Team</Name>
<UserScreenSet>
<AllScreens>
<UserScreen>
<Bounds>
<Left>0</Left>
<Top>0</Top>
<Width>2560</Width>
<Height>1600</Height>
</Bounds>
<WorkingArea>
<Left>0</Left>
<Top>0</Top>
<Width>2560</Width>
<Height>1600</Height>
</WorkingArea>
<Primary>true</Primary>
<DeviceName>\\.\DISPLAY1</DeviceName>
</UserScreen>
</AllScreens>
<Name>&lt;Window Layout-specified&gt;</Name>
</UserScreenSet>
<EnableSnapping>true</EnableSnapping>
<SnapOnSlotActivateKey>false</SnapOnSlotActivateKey>
<SnapCombo>
<Combo>Ctrl+B</Combo>
<Modifiers>Ctrl</Modifiers>
<Key>
<Key>B</Key>
<Code>48</Code>
</Key>
</SnapCombo>
<PiPSqueak>true</PiPSqueak>
<Regions>
<Rect>
<Left>0</Left>
<Top>0</Top>
<Width>512</Width>
<Height>400</Height>
</Rect>
<Rect>
<Left>0</Left>
<Top>400</Top>
<Width>512</Width>
<Height>400</Height>
</Rect>
<Rect>
<Left>0</Left>
<Top>800</Top>
<Width>512</Width>
<Height>400</Height>
</Rect>
<Rect>
<Left>0</Left>
<Top>1200</Top>
<Width>512</Width>
<Height>400</Height>
</Rect>
</Regions>
<Rollover>
<Enabled>false</Enabled>
<Scale>1.5</Scale>
<Rollup>false</Rollup>
<Frames>10</Frames>
</Rollover>
<MainWindow>
<Region>
<Left>512</Left>
<Top>0</Top>
<Width>2048</Width>
<Height>1600</Height>
</Region>
<Border>None</Border>
</MainWindow>
<AlwaysOnTop>false</AlwaysOnTop>
<RenderSize>
<Width>2048</Width>
<Height>1600</Height>
</RenderSize>
<FocusFollowsMouse>true</FocusFollowsMouse>
<DisableInstantSwap>false</DisableInstantSwap>
<DisableAlwaysDeactivate>true</DisableAlwaysDeactivate>
</WindowSnapperProfile>
<WindowSnapperProfile>
<Name>Mag Vynd Team</Name>
<UserScreenSet>
<AllScreens>
<UserScreen>
<Bounds>
<Left>0</Left>
<Top>0</Top>
<Width>2560</Width>
<Height>1600</Height>
</Bounds>
<WorkingArea>
<Left>0</Left>
<Top>0</Top>
<Width>2560</Width>
<Height>1600</Height>
</WorkingArea>
<Primary>true</Primary>
<DeviceName>\\.\DISPLAY1</DeviceName>
</UserScreen>
</AllScreens>
<Name>&lt;Window Layout-specified&gt;</Name>
</UserScreenSet>
<EnableSnapping>true</EnableSnapping>
<SnapOnSlotActivateKey>false</SnapOnSlotActivateKey>
<SnapCombo>
<Combo>Ctrl+B</Combo>
<Modifiers>Ctrl</Modifiers>
<Key>
<Key>B</Key>
<Code>48</Code>
</Key>
</SnapCombo>
<PiPSqueak>true</PiPSqueak>
<Regions>
<Rect>
<Left>0</Left>
<Top>0</Top>
<Width>512</Width>
<Height>400</Height>
</Rect>
<Rect>
<Left>0</Left>
<Top>400</Top>
<Width>512</Width>
<Height>400</Height>
</Rect>
<Rect>
<Left>0</Left>
<Top>800</Top>
<Width>512</Width>
<Height>400</Height>
</Rect>
<Rect>
<Left>0</Left>
<Top>1200</Top>
<Width>512</Width>
<Height>400</Height>
</Rect>
</Regions>
<Rollover>
<Enabled>false</Enabled>
<Scale>1.5</Scale>
<Rollup>false</Rollup>
<Frames>10</Frames>
</Rollover>
<MainWindow>
<Region>
<Left>512</Left>
<Top>0</Top>
<Width>2048</Width>
<Height>1600</Height>
</Region>
<Border>None</Border>
</MainWindow>
<AlwaysOnTop>false</AlwaysOnTop>
<RenderSize>
<Width>2048</Width>
<Height>1600</Height>
</RenderSize>
<FocusFollowsMouse>true</FocusFollowsMouse>
<DisableInstantSwap>false</DisableInstantSwap>
<DisableAlwaysDeactivate>true</DisableAlwaysDeactivate>
</WindowSnapperProfile>
</ArrayOfWindowSnapperProfile></SerializedObject>
</Box>

Lax,

Hey, got it working!

It was actually not exporting any changes I made to the game and was giving me a "FTL Modifiers 'Shift' in too many places" bug that I couldn't figure out yesterday. It still seems pretty arcane, but by clicking through every possible option in the Character Sets I finally found it.

So the problem wasn't the code itself, it was the fact that the code wasn't updating. That answers a lot of other questions I'd been having too.

I used your window layout settings as best I could (everything but your massive region size... thats what she said?) and the feature worked correctly with both the dev and non-dev builds of Inner Space; I could mouse over any of the game windows, watch it focus as I moved, and type and/or click in the window without clicking or using a hotkey to focus it first.

It does only work if one of the game windows is currently in focus (i.e. if a browser window is focused, you will have to click or use a hotkey to focus a game window first)... but that doesn't sound like the problem you're having with it.

What version of Windows is this on? I'm currently testing on Vista (64-bit but that doesn't matter) but it should work equally well on XP or 7.

Oh ;) Yeah that would do it.

About the FTL modifiers thing, I will have to do a better explanation of that because the box is somewhat confusing. Probably more so because people are moving to 36 from 35 and not understanding why they get this error.

There's a few different ways to fix this, depending on why you're getting it ;) if you have "Use FTL Modifiers" enabled on a Key Map (not a mapped key) that gives this error, it's probably a good idea to uncheck it unless you actually intended for every keystroke to send the FTL modifiers. The way the Quick Setup Wizard sets up FTL, Use FTL Modifiers should be enabled for 3, and only 3, Mapped Keys: FTL Target Me, FTL Assist Me, and FTL Follow Me.

If one of those mapped keys gives the error, then the Key Combination in the WoW Macro Action it uses has a modifier that conflicts with selected FTL modifiers. For example, FTL Follow Me uses F11 by default. If you change it to Shift+F11, then the FTL wont work correctly if any character has Shift selected.

ISBoxer 35 didn't detect this, people instead came and said something like "my slaves wont follow 2 of my guys but it works from the others". Now ISBoxer 36 detects it and the message confuses people ;)

Lax,

Thanks for the replies. Sorry to have you check out my region stuff when that wasn't actually the problem.

I understood everything in the popup message except the FTL 'Shift'. I had no idea what that meant since I don't even use the FTL functionality (just used the Quick Setup and that code came along for the ride, and I promptly took the FTL DPS Key Map out on both my teams).

I must say, though, ISBoxer is really very nice. I spent 8 hours trying to get one boss down yesterday and today with some ISBoxer configurations I finally got him down. Thanks again!