Log in

View Full Version : [Mojo] Build 13 - Bug Report



Fursphere
12-26-2009, 01:27 PM
I don't see a mojo bug report thread, so I'll start one.

Build 13 - Broadcasting only.

I just received a Razer Naga mouse as a gift, so I figured I'd use Mojo to get things rolling. The software flat-out REFUSES to pass the NUMPAD 2 button. Either on the mouse or on the keyboard, it won't pass.

I have verified both buttons (keyboard and mouse) to be working outside the software, so no problems there.

Also, the lack of a broadcast on / off toggle key is killing me! How am I supposed to chat? lol

thanks

-Fur

Fursphere
12-26-2009, 02:05 PM
Also, not really a bug - but Mojo does interfere with Input Director KVM operations. Running both at the same time gets some strange results (things like mouseover to next PC just randomly start/stop working)

Freddie
12-26-2009, 03:13 PM
I don't see a mojo bug report thread, so I'll start one.

Build 13 - Broadcasting only.

I just received a Razer Naga mouse as a gift, so I figured I'd use Mojo to get things rolling. The software flat-out REFUSES to pass the NUMPAD 2 button. Either on the mouse or on the keyboard, it won't pass.

Thanks for the report. Is NumLock on? If this still happens with NumLock on, could you please copy and paste the info that appears in "Your last action" when you press Numpad2 on the keyboard. Thanks.

Edit: I just tested this and it works okay on my computers with both PS2 and USB keyboards.

When NumLock is on, Numpad2 sends a 2 character. With NumLock off, the same key sends a down-arrow character.

To the operating system (and to Mojo) those are two different keys even though the same piece of plastic is used.


[Also, the lack of a broadcast on / off toggle key is killing me! How am I supposed to chat? lol
Click the green Broadcast button on the main screen. There will be other ways to do this in future bulids, but for now, that's the only way.

Freddie
12-26-2009, 03:41 PM
Also, not really a bug - but Mojo does interfere with Input Director KVM operations. Running both at the same time gets some strange results (things like mouseover to next PC just randomly start/stop working)
Mojo shouldn't have any effect on other KM programs unless the mouse cursor leaves the local display.

If Mojo is affecting Input Director without the mouse cursor going past the edge of the display, it's a bug or design flaw in one or both programs.

I don't think Mojo has either but I'll look at the source code again and try to make sure.

Fursphere
12-26-2009, 04:01 PM
The numlock thing - every other numlock button works fine. Its just NUMLOCK 2. Thats what tipped me off - I use 1 - 5 for healing. 1,3,4,5 were working, but 2 just wouldn't go. I made sure it wasn't the new mouse by using the keyboard - same result.

When I used software boardcasting in the past, I just F12 to toggle on / off the boardcasting fuctionality. That's what I was referring to above - having to alt-tab and click a box isn't realistic.

The "mouse over" part of MOJO basically replicated what Input Director does now. (although if the mojo window is "active" it won't pass over to the next PC, I have to click on the desktop then it'll pass...). Mojo is *almost* perfect in its basicaly functionality - for me. :)

I'm old school. No key maps. No do not pass lists. I just want "on and off" broadcasting. lol

Freddie
12-26-2009, 04:18 PM
The numlock thing - every other numlock button works fine. Its just NUMLOCK 2. Thats what tipped me off - I use 1 - 5 for healing. 1,3,4,5 were working, but 2 just wouldn't go. I made sure it wasn't the new mouse by using the keyboard - same result.
Could you click "Geeky stuff" on Mojo, try to broadcast Numpad2, and copy the messages that Mojo displays so I can see them?


When I used software boardcasting in the past, I just F12 to toggle on / off the boardcasting fuctionality. That's what I was referring to above - having to alt-tab and click a box isn't realistic.
I understand. You'll be able to toggle it with a hotkey. Like I said, it will be in future builds.


The "mouse over" part of MOJO basically replicated what Input Director does now. (although if the mojo window is "active" it won't pass over to the next PC, I have to click on the desktop then it'll pass...). Mojo is *almost* perfect in its basicaly functionality - for me. :)
Well let's try to get it perfect! :)

Does this problem with Mojo active/inactive happen when Input Director is not running?

Fursphere
12-26-2009, 05:41 PM
Ok - the mouseover thing seemed to be a conflict between Mojo and input director. I did a full reboot and shut down input director before starting mojo, and the problem is gone. It no longer cares if its foreground or background - mouse passes over to next PC either way. :D

Numlock thing: How do I test this WITHOUT WoW running? I'm used to software broadcasting being "on or off" - not program specific. It seems the broadcasting on works "inside" of WoW ?

EDIT: used the login screen to test.

Ok, it seems to be working fine now (weird!). Its either an incompatiblity with Input Director, or something wonky when I first launched Mojo? Anyway, it works now.

Couple of notes, as I think you may already be aware of:

1) Mouseover enabled kills broadcasting. :( Can't use both at the same time right now.
2) All of the buttons "WoWs" "Toons" "Teams" don't seem to do anything with a multiple PC setup. I've seen screenshots of them doing stuff - so I'm assuming its just my setup.
3) A feature that would turn numlock on on all PCs when WoW launched would be awesome. I currently use a little utility and a batch file to do this - so they're all synced when I fire up WoW.

Fursphere
12-26-2009, 05:47 PM
I'm using Windows 7 Pro on all clients btw. Launching Mojo causes the Windows UAC to throw a fit. ;)

I have to "authortize" it every time I launch it.

The selective broadcasting is a mixed blessing for me too. I like that its not always on - and only auto-enables itself when it detects WoW running - but I've also gotten used to have it broadcast in Windows, so I use it quite often (mass launch programs and also how I launch WoW x5)

Freddie
12-27-2009, 01:19 AM
Ok - the mouseover thing seemed to be a conflict between Mojo and input director. I did a full reboot and shut down input director before starting mojo, and the problem is gone. It no longer cares if its foreground or background - mouse passes over to next PC either way. :D
Okay, that's what I guessed. Two KM programs running at the same time are like two male alpha gorillas in the same house. :)


Numlock thing: How do I test this WITHOUT WoW running? I'm used to software broadcasting being "on or off" - not program specific. It seems the broadcasting on works "inside" of WoW ?

EDIT: used the login screen to test.
That's how I test too (with WoW's log in screen). This build of Mojo only broadcasts to WoW. You can't test it with any other program. My plan is to make Mojo work perfectly with WoW, then later add more games.


1) Mouseover enabled kills broadcasting. :( Can't use both at the same time right now.
Right, that's temporary. The program is going to do three different things (broadcast, mouseover, and hotkeys). These things conflict with each other to some extent so I'll probably get all three working before I try to make them cooperate. Maybe I should change the green buttons so only one is on at a time.


2) All of the buttons "WoWs" "Toons" "Teams" don't seem to do anything with a multiple PC setup. I've seen screenshots of them doing stuff - so I'm assuming its just my setup.
Toons was enabled in an earlier build but it didn't really do anything so I turned it off in build 13. Right now I'm writing the real code for those buttons, and they will all gradually begin to work for real in the next few builds.


3) A feature that would turn numlock on on all PCs when WoW launched would be awesome. I currently use a little utility and a batch file to do this - so they're all synced when I fire up WoW.
Okay, I'll add that when I do the "launch WoW" stuff. That may be in the next build, I'm not sure yet.

Freddie
12-27-2009, 01:35 AM
I'm using Windows 7 Pro on all clients btw. Launching Mojo causes the Windows UAC to throw a fit. ;)

I have to "authortize" it every time I launch it.

This happens because Mojo tells the OS that it needs administrative privileges every time it runs because if it doesn't have them, it can't send keystrokes to programs that are running as admin and it will appear to be broken.

HotkeyNet doesn't do this, and as a result, people constantly think HotkeyNet is broken when actually they just need to run it as admin. I decided to avoid this problem with Mojo by making it require admin privileges on its own.

If you have a better idea about how to handle this, please tell me.


The selective broadcasting is a mixed blessing for me too. I like that its not always on - and only auto-enables itself when it detects WoW running - but I've also gotten used to have it broadcast in Windows, so I use it quite often (mass launch programs and also how I launch WoW x5)
This opens up a couple of different issues so please bear with me.

1. I think you're talking about broadcasting to computers rather than broadcasting to windows. Is that right? Those two things are actually quite different from each other. Broadcasting to a computer is what mouseover does when you're moused over, except it only does it with one computer. I could very easily make a fourth mode of the program (in addition to mouseover, broadcast, and hotkeys) where it broadcasts to all computers simlultaneously. Is this what you mean?

2. As far as broadcast-to-windows goes, I'm planning to implement it one game at a time. First I'm going to make it work as perfectly as possible with WoW.

3. As far as launching goes, I'm planning to handle that through the GUI, not through broadcast. The "WoW" and "Team" and "Toon" screens will be used for that. This may be in the next build. In other words, you'll be able to right click a toon or a team and select "launch" and that toon or team will get launched. But maybe this is too automatic and you'd rather do it manually with broadcast.

What do you think?

Fursphere
12-27-2009, 02:48 AM
This happens because Mojo tells the OS that it needs administrative privileges every time it runs because if it doesn't have them, it can't send keystrokes to programs that are running as admin and it will appear to be broken.

This makes perfect sense, and is actually a good thing. I'll just have to figure out how to modify a shortcut in Win7 to have it auto-launch as admin. I'm a Win7 newbie. :)




Right. Keep in mind i'm a long time hardware broadcaster. With my Vetras - there is no "on" or "off" states. If I'm using the broadcasted keyboard - its broadcast to all PCs. To not broadcast to a particular PC - I had to physically unplug the input cable (Ps/2 in my case).

But this brings up an interesting option. The main window to Mojo - it shows you all the conntected computers. Perhaps you could "click" on the ones that you want enabled for broadcasting? (or mouseoever?). Just an idea.

[quote]2. As far as broadcast-to-windows goes, I'm planning to implement it one game at a time. First I'm going to make it work as perfectly as possible with WoW.

Understood. This makes sense - but maybe you could have it show what window its "hooked" too (obviously WoW, but maybe just some kind of GUI indicator that it detected WoW and is going to broadcast to it?).


3. As far as launching goes, I'm planning to handle that through the GUI, not through broadcast. The "WoW" and "Team" and "Toon" screens will be used for that. This may be in the next build. In other words, you'll be able to right click a toon or a team and select "launch" and that toon or team will get launched. But maybe this is too automatic and you'd rather do it manually with broadcast.

This is what both Keyclone and Innerspace/ISBoxer are doing. Seems to be the norm - so I'd go with it. Would make things *really* simple for cross PC communication.

What I've always done is just put the WoW launch icon at the top of my Windows Start menu. When I wanted to launch all clients:

"start button" or "control esc"
"down arrow"
"enter"

....and that would fire up WoW on every computer. This is just my personal habits. Everyone does it differently. Being that I started with just straight broadcasting, my approach to multiboxing is often quite different from other peoples. I tweak the program (game) to work around the broadcasting - it seems 99% of the newer folks tweak the broadcaster (software) to the game. I'm backwards. :D


Okay, that's what I guessed. Two KM programs running at the same time are like two male alpha gorillas in the same house

So, after another round of reboots, everything seems to be playing nicely. Input Director starts with Windows. I use it for the "mouseover" KVM functionality only - going from PC to PC.

I launched MOJO after that, and it seemed to play just fine. I turned off the "mouseover" button, and only turned on the "broadcasting" button - everything went fine. There was on pull in H UK where CTRL and ALT seemed to get "stuck" - I had to hit them a few times each to get them to clear. I wasn't able to reproduce the error, so I can't tell you what caused it.


Right, that's temporary. The program is going to do three different things (broadcast, mouseover, and hotkeys). These things conflict with each other to some extent so I'll probably get all three working before I try to make them cooperate. Maybe I should change the green buttons so only one is on at a time.

That would make things less confusing on the surface for sure. :) Also I don't see a way to tell which copy of MOJO is "master". Again, I'm running it on multiple PCs where most people aren't - so i'm the odd man out.

Freddie
12-27-2009, 03:29 AM
This makes perfect sense, and is actually a good thing. I'll just have to figure out how to modify a shortcut in Win7 to have it auto-launch as admin. I'm a Win7 newbie. :)
On Vista, you have to disable UAC to do that and I'd expect it's the same on Win 7. Maybe there's a way to disable it just for that one program but if so you'll probably have to disable it again when Mojo updates to the next build. Personally I love UAC and knowing what it's doing, I don't mind the prompts.


Right. Keep in mind i'm a long time hardware broadcaster. With my Vetras - there is no "on" or "off" states. If I'm using the broadcasted keyboard - its broadcast to all PCs. To not broadcast to a particular PC - I had to physically unplug the input cable (Ps/2 in my case).
That's a good way to think about it. This is like hardware broadcasting. This didn't occur to me since I've never used any hardware KVM stuff or swtiches or anything of that sort.

What do you think about a fourth button at the top of Mojo's window for "hardware broadcasting"? Maybe that's too confusing. I've been hoping that somehow hardware broadcasting can be merged invisibly into some other part of the interface.


But this brings up an interesting option. The main window to Mojo - it shows you all the conntected computers. Perhaps you could "click" on the ones that you want enabled for broadcasting? (or mouseoever?). Just an idea.
Good idea. Let's talk about this in more detail as that screen develops. Those PCs will have a right click menu (all icons will have right click menus). The PCs can change appearance to indicate various things such as whether they are receiving broadcasts. There can also be what Microsoft calls a tooltip which means text appears when the mouse cursor hovers over the picture.

(continued below)

Freddie
12-27-2009, 03:47 AM
Understood. This makes sense - but maybe you could have it show what window its "hooked" too (obviously WoW, but maybe just some kind of GUI indicator that it detected WoW and is going to broadcast to it?).
The "WoW" screen will have an icon for each Wow on the network, and the icons will show somehow which ones are running, which ones are receiving broadcasts, etc. Is that what you mean?


What I've always done is just put the WoW launch icon at the top of my Windows Start menu. When I wanted to launch all clients:

"start button" or "control esc"
"down arrow"
"enter"

....and that would fire up WoW on every computer. This is just my personal habits. Everyone does it differently. Being that I started with just straight broadcasting, my approach to multiboxing is often quite different from other peoples. I tweak the program (game) to work around the broadcasting - it seems 99% of the newer folks tweak the broadcaster (software) to the game. I'm backwards. :D

I think you're exactly right. I'd like Mojo to be flexible so people can use it however they like. You've convinced me to make it emulate hardware broadcasting.


I launched MOJO after that, and it seemed to play just fine....
The order in which you launch Input Director and Mojo may make a difference because probably both programs are installing low level hooks, and depending on which one installs first, one of them can hide keyboard and mouse events from the second. (This can happen inadvertently.) I think the one that installs second can hide events from the first but maybe it's the other way around. I try to write Mojo so it never hides anything.


Also I don't see a way to tell which copy of MOJO is "master". Again, I'm running it on multiple PCs where most people aren't - so i'm the odd man out.

There isn't any master. All copies of Mojo have the same abilties. No masters, no slaves, no servers, no clients. Just Mojos. :)

Edit: However the settings on one Mojo don't necessarily affect another Mojo. This may change as the program develops. Right now, for example, if you set mouseover layout on one PC, it doesn't affect the mouse that's plugged into another PC. You need to set the second PC's mouseover layout separately if you want to mouse over with that PC's mouse.

Fursphere
12-27-2009, 12:44 PM
There isn't any master. All copies of Mojo have the same abilties. No masters, no slaves, no servers, no clients. Just Mojos.
Edit: However the settings on one Mojo don't necessarily affect another Mojo. This may change as the program develops. Right now, for example, if you set mouseover layout on one PC, it doesn't affect the mouse that's plugged into another PC. You need to set the second PC's mouseover layout separately if you want to mouse over with that PC's mouse.

I actually figured this out last night. The Input Director + Mojo setup an yeild some quite interesting results

When I mouseover to another screen with ID - that becomes the lead computer for "input" Mojo sees this, and depending on each PC's Mojo settings, different things happened. (broadcast on or off).

So the "main" was where ever my mouse was, and the broadcasting was done on a PC mojo window basis. Took me a minute to figure out what was going on. :)

Also, whats up with the install path for Mojo? I'm used to things going in Program Files - not Users\Appdata\roaming profiles? Seems a bit odd to me.

Freddie
12-27-2009, 03:39 PM
Also, whats up with the install path for Mojo? I'm used to things going in Program Files - not Users\Appdata\roaming profiles? Seems a bit odd to me.
It uses Microsoft's ClickOnce deployer. The location is normal for ClickOnce. ClickOnce always caches binaries in %appdata%.

You can copy Mojo's files and put them somewhere else if you want.

http://msdn.microsoft.com/en-us/library/t71a733d(VS.100).aspx

Fursphere
12-27-2009, 04:10 PM
Ahh Microsoft... all makes sense now. lol

Freddie
12-27-2009, 04:49 PM
People often think ClickOnce is weird. I did too when I first saw it. But if you look at what it does (updates Mojo automatically) instead of how it does it (caches Mojo in hidden directory) I think it's a pretty good fit for Mojo.

The only real objection I've heard is that some people's %appdata% is on a small SSD and they don't want to put stuff on that SSD. But Windows lets people move %appdata% to another hard disk if they want, so that's not a problem.

Earlier versions of ClickOnce had a problem with vanishing desktop shortcuts but that seems to be fixed in the new beta version that Mojo's using.

If there are problems with ClickOnce or it turns out to be buggy (previous versions were buggy) I'll replace it with a traditional installer. I'm just trying it out and seeing people's reactions.

Fursphere
12-27-2009, 06:42 PM
FYI - I just pulled my Vetra multiplexers out of my rack. (and about a dozen cables...)

I'm feeling a little strange right about now.

Freddie
12-27-2009, 06:59 PM
Holy crap. :)

What made you decide to do it?

Fursphere
12-27-2009, 07:12 PM
Damn Razer Naga mouse was the catalyst. No way to hardware broadcast this thing....

I'm exclusively using Mojo to broadcast too. Its a litle cumbersome having to click "on" and "off" - but I'm dealing with it. lol

Freddie
12-27-2009, 07:25 PM
I'm totally amazed. I can't think of a better compliment.

I'll add a toggle hotkey as fast as I can, right after I finish the stuff I'm working on for the next build.

(I would add it right now and post a build for you except there's a lot of half finished broken stuff in my current work build, and I can't.)

Fursphere
12-27-2009, 11:02 PM
:)

ok, time for another bug report. doesn't see to be passing SHIFT to slaves - specifically when used as a modifier.

I was trying to pass ? (shift + /). main got a ?, alts got a /

didn't matter if it was right or left shift.

Freddie
12-27-2009, 11:06 PM
That's because I didn't finish the broadcast code yet. The program doesn't yet broadcast shifted characters to remote PCs. I'll do it very soon. (It may not handle alt and ctrl key combinations properly either. I just haven't gotten to that stuff yet.)

zenga
12-27-2009, 11:22 PM
FYI

I'll start using Mojo as my only broadcasting tool as of tomorrow. Need to buy my first windows license ever in my life. And that is if windows doesn't freak me out lol. Got me a new comp that i'll be only using for wow. And the tools that are currently available are either overkill for what i want, or it tastes fishy. Since mojo is opensource this seems to be the only way to go. I'll keep you posted about my mojo adventures :)

Aragent
12-27-2009, 11:46 PM
Noticed two things in the conversation between Fursphere and Freddie

one:
Mojo shortcut, to auto launch as admin in windows 7 ultimate at least this can normally be accomplished by rightclicking the shortcut and go under properties, you then have a choice combatability tab or advanced button, and click run as administrator.

However Mojo is the only shortcut I currently have that does not give me this option. and thus I still have to approve it each time.

I suppose we could Change Permissions of mojo files in the %appData% Folder. Not 100 sure of all the vulnerability repercussions that may cause yet.

Two:
within the Mojo application say the WoW Tab where we will launch wow clients what are your plans in regards to allow this to launch the WoW client with the ability set priority and set Affinity?

If number two: is still a bit of a ways off in development, that discussion can be floored till a more appropriate time, as to not derail more appropriate discussion for the now.

As always Freddie your work is appreciated and Mojo has come a long way in such a short time, I am looking forward to seeing were it leads us.

Fursphere
12-28-2009, 12:06 AM
Another bug:

I mentioned before the ALT and CTRL "sticking" issue. It seems to happen when I mouse over to another screen and alt-tab. Then one (or more) clients will randomly start having the ALT / CTRL kets "stick". Rolling the keys rapidly a few times will fix the problem.

If I can narrow it down further, I wil - but its somewhat random.

Freddie
12-28-2009, 12:07 AM
FYI

I'll start using Mojo as my only broadcasting tool as of tomorrow. Need to buy my first windows license ever in my life. And that is if windows doesn't freak me out lol. Got me a new comp that i'll be only using for wow. And the tools that are currently available are either overkill for what i want, or it tastes fishy. Since mojo is opensource this seems to be the only way to go. I'll keep you posted about my mojo adventures :)

Okay, just please be aware (like I said above) that Mojo doesn't send shifted characters to remote PCs yet. Now that people are starting to rely on the program, I'll do it very soon. (I had forgotten this wasn't done till Fursphere reminded me just now.)

Freddie
12-28-2009, 12:27 AM
Mojo shortcut, to auto launch as admin in windows 7 ultimate at least this can normally be accomplished by rightclicking the shortcut and go under properties, you then have a choice combatability tab or advanced button, and click run as administrator.

However Mojo is the only shortcut I currently have that does not give me this option. and thus I still have to approve it each time.
I don't have Win 7, but if it works like Vista, you're talking about two different things.

The first thing is whether Mojo runs as administrator. Mojo always runs as administrator (if it runs at all). Users have no choice about this. (Except of course they can choose not to let it run.) On Vista, this is the option that appears on shortcuts. There's no reason for this option to appear on Mojo's shortcut because Mojo sets the option to "run as administrator" and the user can't change that.

The second thing is whether you get prompted to approve Mojo's running as administrator when Mojo launches. On Vista, this has nothing to do with settings on the shortcut. It depends on the UAC setting. If you don't want to be prompted, you need to turn UAC off.


within the Mojo application say the WoW Tab where we will launch wow clients what are your plans in regards to allow this to launch the WoW client with the ability set priority and set Affinity?
Yes, there will ways to configure those things for each WoW, and one of those ways will be to right-click a WoW icon on the WoW screen.


As always Freddie your work is appreciated and Mojo has come a long way in such a short time, I am looking forward to seeing were it leads us.
Thanks. I'm looking forward to seeing that too. I don't exactly know myself! :)

Freddie
12-28-2009, 12:35 AM
Another bug:

I mentioned before the ALT and CTRL "sticking" issue. It seems to happen when I mouse over to another screen and alt-tab. Then one (or more) clients will randomly start having the ALT / CTRL kets "stick". Rolling the keys rapidly a few times will fix the problem.

If I can narrow it down further, I wil - but its somewhat random.
Okay, thanks. As soon as I finish the stuff I'm doing now for the next build I'll try to clean up all the loose ends with modifiers going to remote PCs.

Like I said above, I just didn't get around to that stuff yet.

Fursphere
12-28-2009, 01:52 PM
No worries. I'm sure you've got a huge "to do" list as it is. :)

I'm wondering if it isn't my new keyboard though - its been doing some other strange things. I'll have to investigate further.

rocnroll
12-28-2009, 02:05 PM
No worries. I'm sure you've got a huge "to do" list as it is. :)

I'm wondering if it isn't my new keyboard though - its been doing some other strange things. I'll have to investigate further.

Wait, did you say new keyboard? You replaced the venerable PS/2 keyboard? Who are you and what did you do with the real Fur? The next thing you know, you'll stop using the default UI. ;)

Fursphere
12-28-2009, 03:03 PM
Wait, did you say new keyboard? You replaced the venerable PS/2 keyboard? Who are you and what did you do with the real Fur? The next thing you know, you'll stop using the default UI. ;)

Well I put the new Razer Naga next to my Logitech G15 keyboard and noticed how DIM the lights were on the G15 - it bugged the hell out of me. So I replaced it with a new keyboard (that I may take back - its starting to annoy me with some "quirks" it has). :D

My trusty PS/2 keyboard is still plugged into my Belkin KVM switch, which goes to the PS/2 ports on each PC. ;)

Its just now that I'm using software, I can actually use a fancy keyboard, as the vetra has been retired (for now).

Moorea
12-29-2009, 08:40 AM
I'd turn off the light on the naga and keep the g15 :-) [at least that's what I did - the lights heat my hands unnecessarily anyway - you can get the tool to turn on/off lights off the (terrible) razer web site]

zenga
12-31-2009, 11:16 AM
So i installed mojo on this system i have. Need some time to find my way in this windows thing :)

Anyway, i was curious whats the best way to shift my wow-load over both gpu's? Should this be done through a 3rd party program, or is it some setting in windows? A bit lost here ...

Fursphere
01-01-2010, 12:31 PM
So I found a workaround to the UAC thing - you can use the task schedular to run programs at startup with the high privilges.

Problem? The install path to mojo is just too damn ugly. And there is two copies installed, so I don't even know which one is which.

I think this is my install path?


C:\Users\Andrew\AppData\Local\Apps\2.0\BOJJ0OB1.Y4 4\JZWDBPRY.3M2\mojo...exe_c6b5d4e845ecfd15_0000.00 00_none_d47df8f0b1616ac2

But I've got another mojo.exe is this folder:


C:\Users\Andrew\AppData\Local\Apps\2.0\BOJJ0OB1.Y4 4\JZWDBPRY.3M2\mojo..tion_c6b5d4e845ecfd15_0000.00 00_39147d916e5324b5

Help! :D

Freddie
01-01-2010, 01:06 PM
My guess is that one of those folders is the previous version of Mojo. But the folders are ClickOnce's private info and I'm only guessing.

People are not supposed to need to look at those folders (that's why the names are ugly), and if they do, then I'm doing something wrong. Maybe I should add or change something so UAC can be turned off for Mojo in a convenient way. Or maybe Mojo needs a traditional MSI installer that puts the binaries in a user-selected directory.

In the meantime, as a tester, you can find Mojo's "real" installation folder by launching it from the Start Menu or desktop shortcut. Then click "Show installation directory" on the Debug menu.

Fursphere
01-01-2010, 01:37 PM
I've only installed Mojo a single time - so I'm really lost as why I have two folders? :)

Freddie
01-01-2010, 02:20 PM
We really shouldn't need to know about those folders, but out of curiosity, I just looked inside them. The one whose name begins mojo..exe contains Mojo's files. The one whose name begins mojo..tion contains those same files plus a few extra that are used by ClickOnce.

I'm trying to imagine why ClickOnce needs two copies of the executables. Maybe it has something to do with updating the installation while the program is being used. (The copies used to launch the program have to remain unchanged until the program shuts down.)

If you really want to know, you could try asking in Microsoft's ClickOnce forum:

http://social.msdn.microsoft.com/forums/en-US/winformssetup/threads/

Aragent
01-02-2010, 11:59 AM
Is it possible to select the video card for WoW to run on, like isBoxer?

Was asked over on the Mojo FAQ Forum,

I thought this would be a better place to discuss Possible future features, than the FAQ Forum

I would think if this could be implemented or at least designed to be able to implemented at a later date without having to greatly redo whats already been done. that this would be a great addition.

I know W7 has made great strides in Dual Video cards however I believe this ability as (ISBoxer) implements it helps utilize the second card for multiboxing to a fuller extent.

and thus I would look forward to seeing this feature added at a future date.

Freddie
01-02-2010, 01:23 PM
I don't know. I haven't looked into this.

Something to think about, though. Video cards are nearly doubling in power every year. Games are becoming more demanding at a much slower rate because they are mainly designed for game consoles.

By the time Mojo is mature, in about two years, video cards will be four times faster than they are now and game graphics will have changed much less.

By that time, it's possible that multiple graphics cards will be a fad whose day is done.

Fursphere
01-02-2010, 01:47 PM
Ok, nailed it.

With broadcasting enabled, when I alt-tab (which only alt-tabs on the "Main" machine) it causes the alt keys to "stick" upon going back to the game. I have to tap it a few times to get mojo to realize it "released".

Freddie
01-02-2010, 02:04 PM
Thanks a lot. I'll look at the source code and try to figure out why this is happening and fix it.

Freddie
01-06-2010, 11:45 AM
:)

ok, time for another bug report. doesn't see to be passing SHIFT to slaves - specifically when used as a modifier.

I was trying to pass ? (shift + /). main got a ?, alts got a /

didn't matter if it was right or left shift.
I think this is fixed in build 14, but the code is unlike anything I tried before, so it may have problems. Please let me know.

Freddie
01-06-2010, 11:46 AM
Ok, nailed it.

With broadcasting enabled, when I alt-tab (which only alt-tabs on the "Main" machine) it causes the alt keys to "stick" upon going back to the game. I have to tap it a few times to get mojo to realize it "released".
I didn't get a chance to work on this in build 14, but I think I know what's wrong and I'll get to it soon.