Build 6 has mouseover (KM)

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

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

[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/showthrea...114#post249114