Build 6 has mouseover (KM)

[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.