x64 Replacement/Alternative to Microsoft's IntelliMouse application.
Forum rules
Please read the forum rulesbefore posting for the first time. The more information you can provide, the quicker and more accurately someone can help.
NOTE: To reduce spam, new users can not post links, files or images until they have at least 4 posts.
You can get the beta HERE. Note that this link will always get you the latest beta version!
Changes since v2.8 Beta 9:
#232 - Added more space to new labels so translated text fits better.
#227 - Fixed issues with unicode text/keys for layer names, run application names, simulated keystrokes. Please check that your simulated keystrokes still work (and now work where they did not before in the case of unicode characters)
There is one extra translation for this release; "Window Caption"
Any problems, PM me a copy of the log file (or post a snippet in a code block here).
Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]-- Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
Just installed beta 11. All my simulated keys shortcuts are gone and setting it up again doesn't work either. Reverting back to beta 5 (that was where I was coming from) doesn´t fix them but at least I can set it up working again.
What language and regional settings do you use (I cant see its not English but it doesn't say what it is).
I (thought I) fixed a problem with unicode character sets - which may have caused this.
Are you saying you couldn't "fix" it in beta 11? What happened when you tried to apply the settings?
Unfortunately the log does not indicate any problems. I dont suppose you kept a copy of the XMBCSettings.xml before/after?
Can you send me a copy of this settings file as it is now, so I can use it on an upgrade and try and see why it breaks?
It looks like I need to spend some more time on this!
Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]-- Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
My Windows 8.1 Language is English (UK), regional Settings Spanish (Spain).
What I meant was that in beta 11, after losing all my simulated keys settings, I tried to remake some of them for google chrome, like [CTRL}{TAB}, and while in settings XMBC recognized the shortcut with the yellow overlay, nothing happened in chrome. This behavior was constant in other programs and with different shortcuts. Also tried to reset the layer with similar resuls.
In the link, there are before and after settings and a picture of the effect in the layer.
Having the same problem.
When I load beta9 setting, all Japanese character doesn't show correctly, because the old setting file was saved as ANSI.
So, I converted the encoding of the setting file from ANSI to utf-8 manually and try to start XMBC again.
Now Japanese text shows correctly, but window title containing Japanese doesn't match to the rule, including modern UI app. So, they don't work.
Additionally, when I modified the setting, all simulation key settings was removed from saved setting file.
Thanks to those of you that pointed out <above> the significant bug in the last couple of beta's. I fixed that one and found some other issues with the simulated keystrokes introduced back in 2.8 beta 2. I'm much happier that the code is doing what it should now but please check for youself!
You can get the beta HERE. Note that this link will always get you the latest beta version!
Changes since v2.8 Beta 11:
#227 - Fixed new issues with unicode text/keys for layer names, run application names, simulated keystrokes.
#225 - Fixed occasional crash in new SendInput thread.
Thanks,
Phil
--[ Phil ]--
--[ Administrator & XMBC Author ]-- Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
I'm also getting inconsistent response with beta 12. While shortcuts like {CTRL}{MWUP} or {CTRL}{TAB} works, others like {CTRL}W or {CTRL}T don't.
It seems whatever isn´t between brackets doesn't get recognized because with an "{CTRL}T during" while in chrome, when I hold the button and move the mouse wheel it does zoom the webpage so the {CTRL} part works.
I hope I´ve explained myself correctly.
Don't know what's wrong with this last one, it just leaves my computer almost blocked, keyboard and mouse takes a while to respond and pointer goes jumping instead of sliding. Everything comers back to normal after I force exit XMBC. My OS Lang. is English UK, input Spanish. Reverting back to the beta before this one everything back to normal. Sorry this is causing you such a headache.
When you say this one you mean beta 13? and beta 12 does not do this? Odd. When I installed beta 12 on my laptop it briefly did that lockup thing and then recovered..
Any chance you can get some debug log? Install beta 13 but dont run it, then launch it from the command line with /debug option - then send me the log. I'm unable to reproduce this other than the first time I installed beta 12!
--[ Phil ]--
--[ Administrator & XMBC Author ]-- Logitech G9/G604/M720/MX518, Microsoft Intellimouse, Trust 16341 BT Mouse Windows 10 x64, AMD Ryzen 5900x, MSI x570 Tomahawk, 32GB DDR4,
nVidia RTX 2070s, Evo 970 1Tb NVME, 2x2TB WD Black (RAID1)
