Everything you describe is the behavior of ClickOnce, the installer, which is written by Microsoft. I have practically no control over its behavior except to choose whether or not to use it.
it's impossible to make a real shortcut for a ClickOnce application. ClickOnce installs programs into hidden directories chosen by itself. Like Electron said, ClickOnce creates an entry for Mojo under "Mojoware" in the Start Menu. There's an item on Mojo's menu under debug that shows you the installation directory.
I'll add a menu item to the next build that attempts to recreate the pseudo-shortcut, but obviously if people lose the shortcut, they'll need to launch Mojo without it before they can restore it.
I'm not sure it's a good idea to use ClickOnce. I'm hoping to see a lot of reactions from people before deciding whether to keep it or replace it. When I started using ClickOnce (with HotkeyNet 2) it annoyed me a lot but I've come to love it. The idea of it, which I didn't understand at the beginning, is that Mojo is like a web page and ClickOnce is like a browser and the fake shortcut is like a bookmark to the webpage. Your local copy of Mojo is like a page that your browser has cached temporarily for your convenience. You don't know or care where your browser keeps cached pages, and that's why you're not supposed to care where Mojo is on your hard disk. The real copy is on the web.
Okay thanks.Got the Windows security alert again. Oh well, it's just the built-in firewall doing its job. It correctly identified the software as Mojo so you twiddled the right knob for that.
Let me make a guess of my own. I'm guessing that you're assuming that Mojo sends (for example) shift-down, followed by a letter, followed by shift-up, and this is what makes the letter capitalized.The results on each of the 30 windows was not uniform. The letters were correct and in the correct order. However their shift states were slightly different in each window. It was not the same error in some, but various different errors across most.
From this I suppose that Mojo is sending the key downs and ups, but not specifying what order to perform them in? I wonder if there would be a hit to performance to ensure actions are performed in a sequence? I can think of several ways to do it, but most would probably be wrong since I know nothing about the actual mechanisms in play. Or maybe I have guessed the wrong cause.
That's what I would assume too if I didn't have experience writing software for Windows's keyboard API, but in fact that's not how shift states work. (At least not in this case.) Yes, Mojo sends shift-down and shift-up to WoW, but this has no effect on the shift state. In this case, WoW relies on the operating system to change the shift state, and the operating system doesn't know anything about the broadcasted signals. They are getting sent to WoW not to the operating system.
The only thing that is changing the shift state in this case is your finger. When you press the shift key, the operating system sees your action and changes the shift state. The reason things get out of sync is because the broadcasting takes so much time that it gets delayed relative to your finger actions.
By the way, this is why keys don't get shifted on remote machines. Your finger isn't on their keyboards.(I'll have to find a solution for that pretty soon.)
Mojo's Actions Pane / Log / whatever its called !Excellent! A separate thread is probably a good idea because I don't want to keep these "build" threads going after the next build gets released.I have started to form some ideas about the "Mojo's actions on this PC" frame. Would you like me to start a separate thread on it, or add them here?
Connect With Us