Build 10 -- Configs and more GUI

[Freddie]

Some other feedback on the update process. It may be related to my firewall, not sure. I'm using the free version of Comodo at the moment.

After updating, I launch 2 WoWs and then switch broadcasting on. Then I type in my password. At the first letter on the active WoW window, I get the Comodo firewall prompt for do I want to allow so-and-such? I say yes, but broadcasting still not working. I have to close everything (WoW and Mojo), and then it works fine, and continues to do so until the next update. At least this was the behaviour after updating to build 9 and build 10, and I didn't try build 6 since it was only about mouseover.

So.. is anyone else getting this? *Frowns at firewall icon*

This is happening on a single PC with nothing shown in "Connections?"

[Flekkie]

This is happening on a single PC with nothing shown in "Connections?"

Yes - the Connection Settings are set for "One PC"

[Freddie]

I'll look at the source code and see what it's doing that makes the firewall pop and remove it. Thanks for telling me.

Edit: I think this is fixed now, but I won't post the build till later.

[Flekkie]

Now I've narrowed down when it happens, I'll take a bunch of screenshots and document the next update, in case it happens again.

I have the firewall set very aggressively, so it checks on everything the first time it happens (including things like things like "mojo.exe is trying to modify the user interface of Wow.exe"). I have told it to treat Mojo as a trusted application and Mojo's updater as an installation program, but it doesn't seem to stick between updates. I'm guessing this is a symptom of this ClickOnce software you mentioned before, but its not an educated guess.

[Freddie]

Now I've narrowed down when it happens, I'll take a bunch of screenshots and document the next update, in case it happens again.

Thanks.

I have the firewall set very aggressively, so it checks on everything the first time it happens (including things like things like "mojo.exe is trying to modify the user interface of Wow.exe"). I have told it to treat Mojo as a trusted application and Mojo's updater as an installation program, but it doesn't seem to stick between updates. I'm guessing this is a symptom of this ClickOnce software you mentioned before, but its not an educated guess.

All by itself, without ClickOnce, the updated Mojo will trigger firewalls because it's a different program from the old one. The firewall knows this. You and I think of two Mojo builds as the same program but the firewall doesn't (and shouldn't).