Build 19: Active window tracking

[Fursphere]

I find it super annoying that it's continually mousing over to my internet browser when I don't want it to!

Technically speaking, YOU are mousing over internet explorer. If you don't want to mouse over IE - don't put the mouse cursor there.

[Freddie]

Technically speaking, YOU are mousing over internet explorer. If you don't want to mouse over IE - don't put the mouse cursor there.

Bah technicalities. This calls for one of those jumping mice.

[Freddie]

Build 21 is up with bug fixes and minor changes requested in this thread.

-- I fixed (fingers crossed) Mojo rising to foreground during mouseover.

-- Added progressive disclosure to Active Win Track settings.

-- Changed names of fields on Active Win Track settings.

-- I couldn't fix the crash reported by Moorea but I wrapped the crash location in an exception handler. From now on, when that bug happens, the program should display a message box and keep going. If people can figure out what makes the message box appear, that would be great.

[TheFallenOne]

Active Window Tracking doesn't distinguish one program from another but you might be able to get the effect you want some other way.

For example, you could set all your WoW windows "topmost" (always on top). That way your browser wouldn't cover up a WoW. That's not quite what you want , though.

I'm not entirely sure how it's handled, but Keyclone has a "Focus Follows Mouse" option that makes the mouseover'd WoW the focused window without clicking, and it doesn't use the global Windows setting, AKA it doesn't set the focus to non-WoW windows when they are moused over.

I'm not sure if you'd be able to use the same system as Keyclone to handle the active window tracking in Mojo or not (or even figure out how they handled it), but figured I'd mention it anyways.

[Freddie]

I'm not entirely sure how it's handled, but Keyclone has a "Focus Follows Mouse" option that makes the mouseover'd WoW the focused window without clicking, and it doesn't use the global Windows setting, AKA it doesn't set the focus to non-WoW windows when they are moused over.

I'm not sure if you'd be able to use the same system as Keyclone to handle the active window tracking in Mojo or not (or even figure out how they handled it), but figured I'd mention it anyways.

I guess one way would be, when the OS calls the mouse hook:

1. Call a Win32 function called WindowFromPoint that tells us which window the cursor is in.

2. Check whether that window is on our list of WoWs. (If a program doesn't maintain a list of WoWs, it could call a function that gets the window class name and compare that to WoW's.)

3. If the answer is yes, call SetForegroundWindow.

I could add that to to program as an option. It's just a few lines of code and I don't think it would affect performance noticeably.

[Moorea]

I found a small bug/issue with the latest (21) build:

I changed my network settings for 2 laptop to use ICS (internet connection sharing) [ethernet link between the 2 and 1 of them only on wireless - this is to see if latency is even smaller that way when KMing] and the slave computer was showing as a black screen on the master one (and the master not at all on the slave) until I went into advanced settings and set the master (the one on the computer with the internet connection) to use the private IP from ICS instead of system default - I think Mojo should be smart enough to guess that it should check both sides if I have multiple network interfaces - some explanation of the colors would help too (what does black and yellow mean exactly ? just seems that blue = good and the others are not so good but what exactly?)

[Moorea]

another related issue: if I start a mojo on the other side of the interface that one shows yellow for the middle pc on the outside one (when the ics one works) or if I get back to default setting, the master and 3rd outside work but the one behind the ics is black...

Anyway to have all the PCs showing up as well as (maybe) proxying automatically so the one outside sees the one inside too - through the one it would see ?

I think for the first problem you just need to listen to all interfaces - the proxy part can wait

[Freddie]

Mojo's connection stuff isn't finished yet. With the current build, you if you make a change like that you need to shut down both Mojos and then start them both.

Did you do that?

Edit: For all problems of this type, please let me know if you shut down all Mojos and restarted all of them before you saw the problem. It makes a big difference to me.

The color codes aren't finished. The current scheme is temporary. Blue means two socket connections between the computers; purple means one socket connection (they are connected in one direction but not the other); black means no connection.

[Moorea]

yes I shutdown all mojos in between each try/change as I noticed that exiting 1 doesn't change the status on the other (doesn't detect the deconnection)

[Freddie]

I think for the first problem you just need to listen to all interfaces - the proxy part can wait

Mojo does listen on all interfaces. Please let me know if you shut down all Mojos and restarted them.

Edit: Sorry this crossed your last post.