Build 6 has mouseover (KM)

[Freddie]

Mojo build 6 is ready to test.

Download Mojo (http://www.mojoware.org/p/download.html)

Build 6 has a new feature, mouseover. (The sort of thing that Kavoom and Synergy do.) Configuration is very easy. Just go to Mouseover Settings on the main menu and drag your monitors around. There's also a new button at the top of the main window to turn the feature off and on.

I didn't get a chance to test whether mouseover coexists smoothly with broadcast, so I'd appreciate it if somebody would try and let me know. My intention was that mouseover takes precedence over broadcast, but maybe there's a better way to handle it.

I'd also appreciate comments about the instruction page for the feature. Is the text clear, is it complete, does it contain typos, etc.

Instructions for mouseover on Mojo's website (http://www.mojoware.org/p/mouseover.html)


http://mojoware.org/art/mouseover.gif

[Freddie]

I just want to mention, it's been exactly one month since I started work on Mojo.

I had hoped by today the program's infrastructure would be complete:

-- new program's name
-- website
-- source code depository
-- open source license chosen
-- forum where testers talk to each other
-- installer

And, most important

-- a public build would be available with genuinely useful features so people can start using the program for real.

The last thing is the really hard item. If it turns out that mouseover is free of serious bugs, then I'll be able to say that I met my goals by the one-month deadline.

The mouseover code came from HotkeyNet 2 where it was pretty much debugged, but I may have accidentally screwed it up while transplanting it to its new home inside Mojo.

[Kedash00]

i can't wait to get home and test this new version out! keep up the good work Freddie!

[Fizzler]

Started it up on two PC's. The two clients find each other instantly IP address computer name is all populated.

I use Input Director it is not playing nice with Mojo at all. The slave PC (Input director slave) works fine the mouse movements and clicks are all registering. The Master (Input director master) the mouse movements are sluggish and the double clicks do not register even if I turn off Mouseover.

When I disable Input director it all works fine. What is curious is I am typing on my slave computer the mouse and keyboard are not connected to this computer. Input Director is disable I am using Mojo, but I have broadcasting disabled on both ends and the keys are still being passed from my other computer that has the mouse and keyboard connected to it.

I will mess with it more when I have time I was anxious to try it out.

[zenga]

FYI
Managed to get Build 2 working under 3 windows clients running on 2 different opensuse 11.2 hosts (vmware workstation 6). Must add that I have zero experience with windows, the machines were setup by a collegue. I just installed mojo and tried basic key broadcasting following your instructions. Thought I'd let you know :)

Tried installing mojo under wine, but to no avail so far (no big deal, was just a try).

This project is really promising, and if it turns out to be really good, I might get me my first windows os license ever in my life to run it with wow :D

On a final note, I've been active in several open source projects over the past decade+ (bigger and smaller), and must say that your approach rocks :)

Cheers
z

[Freddie]

When I disable Input director it all works fine.
That's all we can expect. We can't expect two KM programs to run together at the same time.


What is curious is I am typing on my slave computer the mouse and keyboard are not connected to this computer. Input Director is disable I am using Mojo, but I have broadcasting disabled on both ends and the keys are still being passed from my other computer that has the mouse and keyboard connected to it.
Mouseover and broadcasting are separate functions of Mojo. One can be off and the other can be on.

Also, the on/off buttons only stop their computer from sending. They don't stop it from receiving.

[Freddie]

This project is really promising, and if it turns out to be really good, I might get me my first windows os license ever in my life to run it with wow :D
Hehe well if Mojo gets you to buy Windows that will be quite a compliment. :)


On a final note, I've been active in several open source projects over the past decade+ (bigger and smaller), and must say that your approach rocks :)
I'm very glad to hear that. This is the first time I've had anything to do with an open source project, so I have absolutely no idea what I'm doing. I'm just trying to guess what info people would want to see etc.

[Fizzler]

This program works amazingly good when it comes to connection. I have 9 IP addresses on my home network it found the second computer and I did nothing.

Even with Input Director and Multiplicity or Synergy I had to set up IP addresses.

I messed around a little more with the key broadcasting. Is there a Master and Slave? I can see the key states from the first mojo to the second but when I move my mouse to the second PC I do not see the keys being passed to the first mojo. Broadcasting is turned on both directions.

I am calling the first client to start as the first.

[Freddie]

This program works amazingly good when it comes to connection. I have 9 IP addresses on my home network it found the second computer and I did nothing.

Even with Input Director and Multiplicity or Synergy I had to set up IP addresses.
Glad to hear it. My first goal for Mojo is to make it the easiest multiboxing program in the world.


Is there a Master and Slave?
Nope. All Mojos are equal. They all can do the same things.


I can see the key states from the first mojo to the second but when I move my mouse to the second PC I do not see the keys being passed to the first mojo.
Do you mean you're typing on PC 1's keyboard, and

PC 1's mouse is moused over to PC 2, and

WoW is in the foreground on PC 2, and

keystrokes are not getting broadcast to PC 1?

If that's what you mean, it's probably because. I deliberately kept broadcast and mouseover somewhat separate in this build because potentially they can interact in bad ways and I'd like to get them both debugged first.

[Fizzler]

Yes that is just what I meant. Looking very good you have something special in the works here.

[rocnroll]

/agree something very special indeed. Amazing progress for one month (OK, you are reusing code from previous programs). I'm looking forward to month two and beyond!

[Freddie]

Thank you both. I really appreciate the kind words. They mean a lot.

I did reuse a lot of code but even so it was a huge amount of work. This program has a different structure than the earlier ones so everything had to be changed. There's also quite a bit of new code.

The main thing that's new is the broadcasting code. This is my fourth multiboxing program but oddly enough, I never wrote a broadcaster before. This is the first time.

Every piece of code that went into Mojo got cleaned up and done right (well, it got done the best I can, anyway! :) ) so Mojo starts life with a solid foundation. I want this program to be able to grow for years without people running into problems because the foundation is weak.

[Aragent]

Freddie

Just a suggestion, I believe, right now most are letting you do most of the work on the project.
and we are just sitting back and helping test. (Some because we don't know where we can help without hindering your progress.)

However when you get to a point where there are areas that others can help, please post what areas you want help with.

and then others can respond with offers to work on that section.

Great project so far.

[Aragent]

Had Mojo in just mouse-over tonight (Broadcast was turned off) used in place of HKN2

One major problem , Mojo Build 6 I could not build a mouse-over config 4x monitors wide. The Config would brake, (this didn't happen in HKN2)

I could build a 4x monitor con fig 3 wide with the 4th either 1 up or down just fine.

Now I believe the reason for this is that in MOJO Mouse-over Config window has no full screen mode and was not large enough (even though you could stretch the scream wider to accommodate 4 monitors wide once you hit ok, the config screen would go back to initial size and would break and reposition the 4th monitor even though it would leave one or more monitors windows off screen (Had to stretch the screen back out to move them back into the normal size window config.

I could be wrong about why it would not allow 4x wide config However I do hope this helps you in troubleshooting it.

Hope this helps

PS: I am not 100% sure ill try and run numbers latter today but it did feel that Mojo was a bit more Intensive on the local network than HKN2 was, though I was using it in conjunction with HKN with MOJO having Broadcast turned off, and just running mouse-over, there was no other issue than a bit more intensive network activity than using HKN&HKN2 combined Other than the limitation I already mentioned with the Mouse-over config.

[Freddie]

Now I believe the reason for this is that in MOJO Mouse-over Config window has no full screen mode...
I added a maximize button to that window in build 7, which can be downloaded now. Please let me know if you notice any other difference from HKN2.


PS: I am not 100% sure ill try and run numbers latter today but it did feel that Mojo was a bit more Intensive on the local network than HKN2 was, though I was using it in conjunction with HKN with MOJO having Broadcast turned off, and just running mouse-over, there was no other issue than a bit more intensive network activity than using HKN&HKN2 combined Other than the limitation I already mentioned with the Mouse-over config.
What is giving you the impression that Mojo is more intensive on the local network?

What are you actually seeing that makes you think this?


Just a suggestion, I believe, right now most are letting you do most of the work on the project.
and we are just sitting back and helping test.
Testing is incredibly important. That's why I'm publishing builds even during the program's baby stage.

Also, people are doing more than test. They are giving feedback about the design.

Those two things are extremely important. With those two things, the program has a chance of being great. Without them, the program would be lousy.

I can't think of anything else that other people can do at this stage, but if anybody wants to do something in particular, they should send me a PM.

[Owltoid]

My accounts aren't active as i wasn't getting more than 1-2 hours of play time in per week, but once things slow down (or the expansion comes) I'm looking forward to testing out Mojo. Thank you again for all your help, Freddie! I'm glad you've found some assistance in the multiboxing community to develop your project further. If only you enjoyed playing WoW then I'm sure you'd excel at that, too!

[Moorea]

I haven't seen the new UI yet but rather than maximizing the config window to make more room shouldn't you instead shrink the monitors pictures so they fit in the window ? (it's not like there is anything detailed to be done inside each little monitor picture - it's just about relative placement isn't it ?) I think that's how windows desktop extension works; monitors are at scale but scale down depending how you place them

[Freddie]

Ideally, yes, but when I made that screen I drew everything at 1/8 scale to minimize rounding errors in display locations. (Because 8 divides evenly into most LCD sizes).

After I made that screen, I wrote the actual mouseover code, and I think I did it in a way that makes rounding errors irrelevant. But I'm not sure about that, because it hasn't been tested with rounding errors, so for the time being, because I don't want to work on this stuff right now, I'm going to leave the size at 1/8.

[Aragent]

I added a maximize button to that window in build 7, which can be downloaded now. Please let me know if you notice any other difference from HKN2.

Thank you I will test today.



What is giving you the impression that Mojo is more intensive on the local network?

What are you actually seeing that makes you think this?

I been running using HKN and HKN2 for mouseover
I tried HKN and Mojo build6 In Mouseover only
The system just seamed a bit more sluggish a bit more taxed and a little lagging in response this could have been a coincidence, and I dint have any actual latency numbers to back any thing up.

But I will check it today and run some monitoring programs on the net and see if I can get the same responce or if I can get any numbers .


Testing is incredibly important. That's why I'm publishing builds even during the program's baby stage.

Also, people are doing more than test. They are giving feedback about the design.

Those two things are extremely important. With those two things, the program has a chance of being great. Without them, the program would be lousy.

I can't think of anything else that other people can do at this stage, but if anybody wants to do something in particular, they should send me a PM.

I understand just wanted you to know that we respect what your doing and making this an open source project that we appreciate it and a lot of us are willing to do what we can to help the project out.

[Freddie]

The system just seamed a bit more sluggish a bit more taxed and a little lagging in response this could have been a coincidence, and I dint have any actual latency numbers to back any thing up.
Okay, I understand. You observed that Mojo seems slow. Then you made a theory that the slowness is caused by network congestion.

The observation is helpful, especially if we can find a way to measure and see if Mojo really is slower.

There are other reasons why this could happen besides network traffic. For example, Mojo has a different threading model, and maybe I screwed up and one thread is waiting for another too much of the time.


But I will check it today and run some monitoring programs on the net and see if I can get the same responce or if I can get any numbers .
If you learn anything, please let me know.


I understand just wanted you to know that we respect what your doing and making this an open source project that we appreciate it and a lot of us are willing to do what we can to help the project out.
Thank you, I appreciate it. :)

[Marious]

Nice work Freddie seems stuff is working fine, so when can we expect to see some Windower as part of Mojo or will it not include a windower?

[Freddie]

Thanks alot. Mojo's going to include everything that people expect in a multiboxing program.

I'm trying to figure out how to design the screens where people tell the program, "Here's how many WoWs I have, and here's where they live on my hard disk, and here's how I want them laid out on the screen."

I want it to be shockingly easy. :)

[Freddie]

The system just seamed a bit more sluggish a bit more taxed and a little lagging in response this could have been a coincidence, and I dint have any actual latency numbers to back any thing up.
I just noticed something that may explain the difference.

HKN2 has an option in Start Up Settings called Raise Process Priority. This option is on by default. If it's on in your copies of HKN2, then HKN2 will probably be faster than Mojo because HKN2's threads will get scheduled to run sooner when they are ready.

I'll put this setting in the next build of Mojo and we can see if it makes a difference.

[Freddie]

Let's move over to the thread for build 9.

http://www.dual-boxing.com/showthread.php?p=249114#post249114