XMouse Button Control v2.10

[phil]

I've just released X-Mouse Button Control version 2.10

Version 2.10 generally is a bug-fix release but there are a few new features too.
You can find the latest version (including the portable version) in the usual place, on the downloads page (mirror).

For a complete list of changes, check out the version history.
The user guide (included in the installation, and English only right now) can also be found here or here (mirror).

PLEASE NOTE: Do not post bugs or feature requests in this topic. If you find a problem or want something to be added, please create a new topic where your issues or ideas can be discussed.

Once again, many thanks to everyone who has helped me beta test this release, and to all those providing the language packs/translations10

[phil]

OK, I thought I had managed a release without a significant bug.. But I was wrong!
I have just released 2.10.1 to fix a bug with the layer modifier keys.

Now lets see if the auto-update feature works in release mode! You should get a notification of the new version and it should then allow you to download and install the update package automatically.
NOTE: The update mechanism uses DNS so it can take up to 24 hours for the change to be recognised.

Thanks,
Phil

[phil]

Oh, and if you didn't notice, shortly after 2.10.1 came 2.10.2 to fix a lock-up after resuming from sleep (although I'm no longer convinced that it is 100% fixed - let me know if you have any issues).

[NeoZeroo]

Oh, and if you didn't notice, shortly after 2.10.1 came 2.10.2 to fix a lock-up after resuming from sleep (although I'm no longer convinced that it is 100% fixed - let me know if you have any issues).

About that problem when resuming from sleep:
Since Feb 11, when I updated to 2.10 beta 9, it didn't happen at all. Today it happened for the first time though!

I was still at beta 9, but I just checked your following versions and it seems they're not sleeping related, so hopefully this log can still help you.

07-03-2015 22:33:33.0490> HookThread: Successfully set the mouse hook 0xC40397
07-03-2015 22:33:33.0490> HookThread: Successfully set the keyboard hook 0x4E0445
08-03-2015 02:16:33.0483> Power State: System is suspending operation.
08-03-2015 10:49:32.0715> Power State: Operation resuming automatically after event.
08-03-2015 10:49:33.0715> Reinstall mouse hook on resume is enabled. Re-hooking mouse...
08-03-2015 10:49:33.0730> Hook thread exited with result 1
08-03-2015 10:49:34.0322> RemoveMouseHook took 1607ms
08-03-2015 10:49:34.0337> Brightness: Unable to set COM security
08-03-2015 10:49:34.0337> Unloading keyboard layout...
08-03-2015 10:49:34.0337> Current language is 0xF0100416
08-03-2015 10:49:34.0337> Checking installed keyboard layout: 0xF0100416
08-03-2015 10:49:34.0337> Unable to find suitable English keyboard layout... Loading US English.
08-03-2015 10:49:34.0337> HookThread: Successfully set the mouse hook 0x2DCF13E3
08-03-2015 10:49:34.0337> HookThread: Successfully set the keyboard hook 0xCEE1035
08-03-2015 18:29:00.0619> Power State: System is suspending operation.
08-03-2015 18:44:28.0684> Power State: Operation resuming automatically after event.
08-03-2015 18:44:28.0684> Reinstall mouse hook on resume is enabled. Re-hooking mouse...
08-03-2015 18:44:33.0692> Hook thread did not exit in a timely fashion!
08-03-2015 18:44:36.0094> RemoveMouseHook took 7410ms
08-03-2015 18:44:40.0197> Critical section 'LoadSettings' took 4103ms to release!

I've set it to sleep and woke up again after that, but the log stopped at that last line, until I restarted X-Mouse later.

Hope that helps!

[phil]

Thanks for the log... I think something is getting stuck/deadlocked - but its difficult to diagnose as without debug logging,its impossible to see whats getting stuck, and with debug enabled, the deadlock seems to not occur (presumably because things take longer and the deadlock is avoided)!

2.10.2 introduced some code to reset the thread semaphore when resuming but this has not helped 100% although it has only locked up for me once since I released 2.10.2 over a week ago so I think its better but still not perfect.

I clearly need to change the code that dos the waiting to log if the thread is sat waiting for more than a certain time. I will get round to this at some point, probably in 2.11 beta 1 . Then the dodgy code path may become more obvious!

Thanks,
Phil