Build 19: Active window tracking

[Moorea]

another small issue : a multi monitor mojo doesn't show as multi monitor on the other computers mouseover settings screen

[Freddie]

I think Mojo should be smart enough to guess that it should check both sides if I have multiple network interfaces

I'm not sure what you mean by check both sides. Mojo doesn't check anything having to do with IP addresses. Here's how Mojo actually works.

Each Mojo sends out UDP packets to the whole network saying, "I'm a Mojo, call me if you're interested." Meanwhile other Mojos are listening for these packets on all their adapters. There is no special IP address used.

Where the specified IP address comes in (the one you had to change) is that when a Mojo sends out the message, "Call me if you're interested," it has to provide an IP address at which it will be called. In other words, it actually says, "If your'e interested, call me at the following IP address: XX.XX.XX.XX." By default, Mojo lets the OS choose this IP address. That didn't work, so you intevened and chose an address manually. That didn't work either.

What's happening here is (apparently) some peculiarity in the way ICS works. It's possible that it doesn't propagate UDP broadcasts. I don't know anything about ICS. I'll look into it.

[Freddie]

another small issue : a multi monitor mojo doesn't show as multi monitor on the other computers mouseover settings screen

Do they have a blue connection? (Blue in both directions?) They won't show up properly if they aren't connected properly.

[Moorea]

another bug: I set my "bring cursor home" key to Ctrl-Home

when I press that key; it leaves Ctrl stuck on the slave the cursor was in (when going back and using the native keyboard/mouse there everything is like if ctrl is pressed; for instance mouse wheel on firefox zooms in/out instead of scrolling)

[Freddie]

Edit: On second thought, that's probably the same sort of thing as the old Alt-tab problem. Mouseover gets terminated at the instant you press the Home key. Then, a few milliseconds later, you release the Ctrl key, but by then mouseover is no longer happening and therefore the "release Ctrl" signal doesn't get sent to the remote.

I'll have to change something. Thanks for letting me know.

[Moorea]

I'm not sure what you mean by check both sides. Mojo doesn't check anything having to do with IP addresses. Here's how Mojo actually works.

Each Mojo sends out UDP packets to the whole network saying, "I'm a Mojo, call me if you're interested." Meanwhile other Mojos are listening for these packets on all their adapters. There is no special IP address used.

Where the specified IP address comes in (the one you had to change) is that when a Mojo sends out the message, "Call me if you're interested," it has to provide an IP address at which it will be called. In other words, it actually says, "If your'e interested, call me at the following IP address: XX.XX.XX.XX." By default, Mojo lets the OS choose this IP address. That didn't work, so you intevened and chose an address manually. That didn't work either.

it did work (after changing the IP in the drop down) for the simple case of 1 mojo using ics connected to the mojo providing ics; what didn't work after that (2 different tests; 2 different posts) is having both the "inside" and "outside" mojos

so to solve the first case; can you send in that msg all the IPs instead of just one ?

What's happening here is (apparently) some peculiarity in the way ICS works. It's possible that it doesn't propagate UDP broadcasts. I don't know anything about ICS. I'll look into it.

it's windows' built in 0 config NAT and it's kind of handy; I expect several people to use it - but maybe not in the weird setup that I have where I try to save 1 wireless latency yet still use extra computers on both side of that nat

[Moorea]

Nothing is going to work right if they don't have blue connections in both directions.

the bug I reported about screens is unrelated - I go back to a "working" setup - it's related to my request of wrapping in the faq thread but I didn't want to put a bug report there as it's probably very short lived (you'll fix it soon ;-) )

[Moorea]

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.

I think you are color blind (it's ok, no shame, my dad is too) as it's yellow (or maybe mustard rather as it's a dark yellow) and not purple :-)

This being said, more seriously/interestingly, why do you need 2 sockets - a socket is bi directional; so you should only need either of the machine to connect to the other; not both

[Fursphere]

I only get yellowish when my firewall is blocking one or more mojos. But its yellow for sure.

Black for disconnected.

Blue for connected and ready to go.

[Freddie]

so to solve the first case; can you send in that msg all the IPs instead of just one ?

I need to understand why it's not working before I can fix it. I'll have to set up ICS here, watch the programs in a debugger, log their communications, etc.

Edit:

it did work (after changing the IP in the drop down) for the simple case of 1 mojo using ics connected to the mojo providing ics; what didn't work after that (2 different tests; 2 different posts) is having both the "inside" and "outside" mojos

I don't understand the two cases. I don't know what "inside" and "outside" mean.

Every IP address that a computer knows about itself is on its drop down list. If at least one of those IP addresses works, you can select it.

If none of them work, then a human being needs to enter it. Send them all automatically won't help if none of them work.