XMBC 2.21 Beta

[phil]

probably, but that's no excuse for me really is it

[MisfortuneCookie]

Thanks Phil, for continuing to support this software. Regarding the tray icon, I struggle to tell the difference between the disabled and enabled icons. "Pop quiz, hotshot: Is it the slightly more grey version of the icon, or the slightly less grey version of the icon? What's the most you ever lost on a coin toss?"

Now, I'm marginally colorblind, but I don't think there's any color use (on the default layer). Actually, red / green shading for disabled / enabled would probably help significantly, since colors differ qualitative while currently the icons only differ quantitatively. There's also a tiny X on both icons, which make both look like a disabled icon without the context of directly comparing it to the other icon (which I have to do by tapping my enable/disable hotkey twice - every. single. time.). Probably, for the benefit of users with significant color blindness, there should be a pictographic difference between the two.

I'd also love for there to be an option to revert to the default layer on a disable/enable (similar to the option to remember/forget the current layer when restarting).

Thanks for many years of tweaks, experiments, and improvements.

[phil]

Thanks Phil, for continuing to support this software. Regarding the tray icon, I struggle to tell the difference between the disabled and enabled icons. "Pop quiz, hotshot: Is it the slightly more grey version of the icon, or the slightly less grey version of the icon? What's the most you ever lost on a coin toss?"

Now, I'm marginally colorblind, but I don't think there's any color use (on the default layer). Actually, red / green shading for disabled / enabled would probably help significantly, since colors differ qualitative while currently the icons only differ quantitatively. There's also a tiny X on both icons, which make both look like a disabled icon without the context of directly comparing it to the other icon (which I have to do by tapping my enable/disable hotkey twice - every. single. time.). Probably, for the benefit of users with significant color blindness, there should be a pictographic difference between the two.

I'd also love for there to be an option to revert to the default layer on a disable/enable (similar to the option to remember/forget the current layer when restarting).

Thanks for many years of tweaks, experiments, and improvements.

The disabled icon has a red X but is it fairly subtle so I can see how that could be missed at a glance. The tray icons are already all customisable (by placing .ico files in the XMBC settings folder (at least I think that's true of the disabled icon). I will certainly consider adding a reset to default layer on disabled/enabled to the list, but it wont get into v2.21 at this late stage.

[MisfortuneCookie]

The disabled icon has a red X but is it fairly subtle so I can see how that could be missed at a glance. The tray icons are already all customisable (by placing .ico files in the XMBC settings folder (at least I think that's true of the disabled icon). I will certainly consider adding a reset to default layer on disabled/enabled to the list, but it wont get into v2.21 at this late stage.

I'm red/green blind, so I'm probably unable to see the red at its current level of saturation. I tried modifying the icons before, but only through a program that attempted to swap them within the executable. That's great if it's as easy as dropping .ico files into the profile folder, I'll try it out. I can certainly tell the current icons apart when swapping between the two, or when they are placed next to each other, but in the system tray when guessing disabled from enabled I'm no better than chance. It's like guessing whether a room light is at 100% or 75% without looking at the dimmer switch.

Thanks Phil

[phil]

The user guide/manual has a little section near the bottom about changing the icons, gives the filenames etc and where to drop them.
Good luck

[Kukurykus]

That't right, the disabled icon is grey, while enabled white. Maybe it's not big difference, but I can see it (although I don't know if I took attention at it previously). For me it's okay. The other difference beside mentioned (not) colored X symbol in above posts is that disabled icon is also smaller for a reason of being more round, what is especially seen on its bottom corners.

[MisfortuneCookie]

I've been suffering from bizarre interface issues under this beta, or maybe these are useful changes that are flying over my head. It's been presenting this way since the last beta update. Surprise! My hope is that by spacing out my bitching and moaning I can avoid pushing you beyond your rage quit threshold.

(Windows 10 Home N 22H2, geforce 1660, 1920x1080 desktop res, left-aligned vertical taskbar)

The invasive species, "(Left Click["

1.jpg

Inside the "Right Button" settings, "(Left Click[" is nowhere to be found.

1a.JPG

Another example of the "(Left Click[" prefix phenomenon.

1b.jpg

The mysterious alien control panel used to set de-bounce. I want to believe.

2.jpg

[phil]

The last one I see here - I guess something went wrong with the resource order - because the up/down has been attached to the label not the number field. That I can fix easily.

The left click stuff, I don't really understand (and it is not doing that here)... Can you send me a copy of your config/xmbcsettings so I can see if I can reproduce it with that? Unfortunately, I had time to look into this between xmas and before last weekend, but now I have no spare weekends for a while so it might take me a while.

[phil]

Here is 2.21 Beta 41.

Changes since 2.21 Beta 40 (above):

• #896 - Fixed problem in advanced setting screen with spinner for de-bounce time.
• #895 - Re-written the simulated input object to better handle flushing during repeats, and to <try and> prevent
  input (keys/buttons) getting stuck keys when the queue is flushed. A different philosophy and simpler,
  more effective thread synchronization.

I finally found some time to sit and study in detail the various reports about problems with keys/buttons getting stuck in various scenarios.
I believe I may have fixed/improved matters significantly, but its a difficult one to test and be 100% sure about.
I've also completely rebuild my development machine (hardware and software), so hopefully no surprises thrown in from that!

I'm hoping this is getting close to release now, its been far too long - although I am still waiting for a reply from @MisfortuneCookie regarding one of the two items he reported above as I cant reproduce it!

I have built a a portable version of this too if anyone is interested in that:

XMouseButtonControl 2.21 Beta 41 Portable.zip

If you ever see the XBC bugtrap crash window popup (particularly for beta versions) asking you to report the crash, please do so (hit the send report button) and if possible, also contact me here on the forums, Discord or by email so I can try and get to the issue. Whilst the BugTrap logs do often help, they don't always give enough information to diagnose and fix the issue.

As usual, feedback welcome - especially if you find a bug! Any issues/problems, Enable debug logging, make a note of the time the problem occurs and then PM me a copy of the log file (or post a snippet of the last hundred lines or so in a code block here).

NOTE: If you have check for beta versions enabled, you should get notified of a new version and prompted to update in the next day or so. This is the most efficient method (bandwidth wise) as the updates are only ~1/3rd of the size of the full install. Otherwise, you can get the full installation beta HERE. Note that this link will always get you the latest beta version!

[phil]

There may be a problem with some simkeys now (typical)...
If you need to revert to 2.21 Beta 40 until I have fixed it, here is a direct link to it.
But please let me know if you have any problems and need to revert. I want to get this figured out as quick as possible!

[phil]

Here is 2.21 Beta 42.

Changes since 2.21 Beta 41 (a few hours ago!):

• #895 - Of course, it didn't quite work as expected. This *should* fix issues with button held across layers, and missing simulated inputs.

There are potentially more bugs in this. I needed to get .42 our - but now I need sleep! So if you have any serious issues fall back to 2.21 beta 41 (link in the above post).

Portable version:

XMouseButtonControl 2.21 Beta 42 Portable.zip

[phil]

OK well it was quite a big small change I made yesterday (if you get what I mean)...
And today at work I have my first XMBC proper crash in years (as in it crashed and filed a bug report) so I guess I need to make a new version. I think I have found and fixed it but its a nasty in the actual thread synchronization so its tricky to be sure.. Other than test test test.
I also realised I didn't update the version check thus 2.21 Beta 42 (above) was not "advertised". It would still download from the links above but the automatic/built in check for updates didn't see it. I recified that earlier but v2.21 b42 still has that crash I got today.

I'll do a few more checks on 2.21 b43 and update it shortly.

[phil]

Here is 2.21 Beta 43.

Changes since 2.21 Beta 42 (a few hours ago!):

• #895 - Found and fixed a crash that sometimes occurred in the new thread synchronisation code. Need to test further to ensure it is now OK but it was fairly reliable to reproduce and no longer happens.

One additional thing I have noticed, is that due to the changes, the simkey injection is *much* faster now, and this appears to be causing other problems, keys going missing because they are sent (pressed and released) too quickly. This can be mitigated by increasing the global "delay between simulated keystrokes" but it may need some further attention. I will see how it goes, and how many reports of problems I get before making too many more changes (assuming no more crashes).

Portable version:

XMouseButtonControl 2.21 Beta 43 Portable.zip

[phil]

Here is 2.21 Beta 44.

Changes since 2.21 Beta 43:

• #895 - Fixed an issue with simkeys sending and flushing still not addressed in the previous couple of versions.
  Also fixed some more generic thread and memory issues (crash potential).

I have built a a portable version of this too if anyone is interested in that:

XMouseButtonControl 2.21 Beta 44 Portable.zip

If you ever see the XBC bugtrap crash window popup (particularly for beta versions) asking you to report the crash, please do so (hit the send report button) and if possible, also contact me here on the forums, Discord or by email so I can try and get to the issue. Whilst the BugTrap logs do often help, they don't always give enough information to diagnose and fix the issue.

As usual, feedback welcome - especially if you find a bug! Any issues/problems, Enable debug logging, make a note of the time the problem occurs and then PM me a copy of the log file (or post a snippet of the last hundred lines or so in a code block here).

NOTE: If you have check for beta versions enabled, you should get notified of a new version and prompted to update in the next day or so. This is the most efficient method (bandwidth wise) as the updates are only ~1/3rd of the size of the full install. Otherwise, you can get the full installation beta HERE. Note that this link will always get you the latest beta version!

[phil]

just a note for any on 2.21 Beta 41 (and maybe 42, 43) that there *may* be a problem with the automatic check for updates... I noticed that I was not offered the update on my other machines, and running check for updates on the context menu would not do anything obvious. I think that was a bug I introduced in beta 41 (should be fixed now). So either update using the installer from the link above, or in my case, it worked, going to the about XMBC dialogue and pressing check for update in there!