I use the Fire Recognition on Mouse Wheel Scroll feature to change the sound volume. For example scrolling down will send
acSendKeys("{VOLDOWN}")
acSendKeys("{VOLDOWN}")
But when I scroll rapidly it seems that some ticks are missed. The volume changes only slightly compared to when I scroll slowly. Why? How can I fix this?
This is due to each tick firing on its own thread, and there are only 2 Lua engine instances in S+. S+ alternates between whichever engine isn't currently executing a script, but if both are, it discards the action.
This is something which could be improved upon within S+, but it's that way for a reason as it is now to ensure stability (prevent crashes).
The way S+ operates internally, this is definitely a limitation as there's no queue to load actions into for processing. However, that is certainly something I will consider in the future, though it will be rather complicated and may not happen soon.
Updated in 2.8.6.3 to no longer discard mouse wheel gesture events if both Lua states are in use. Now it just queues the other wheel ticks, waiting for the previous ones to finish.
Mouse Wheel Scroll misses ticks
Forum Locked
Posted - 02/12/2016 : 21:41:17
