Author |
Topic |
|
plunt
Italy
88 Posts |
Posted - 12/25/2012 : 03:58:57
|
Option to switches the priority to High once you start drawing a gesture, then resets to Normal when complete. |
Edited by - plunt on 12/25/2012 03:59:42 |
|
Rob
USA
2615 Posts |
Posted - 12/25/2012 : 18:29:19
|
What is the reasoning behind this request? Is it causing a problem? Or you just don't like to see it at High? |
|
|
plunt
Italy
88 Posts |
Posted - 12/26/2012 : 00:27:15
|
No problem with high or normal priority, just to optimize the cpu use. Prioritize the cpu only when gestures are used. |
Edited by - plunt on 12/26/2012 02:00:53 |
|
|
Rob
USA
2615 Posts |
Posted - 12/26/2012 : 08:47:45
|
The reason S+ runs with High is because it's handling every single mouse message and must respond/relay them with the utmost urgency. If priority were Normal and the system were under a heavy load (especially for slower systems), mouse events like clicks and movement could be delayed and disrupt the user's experience.
The priority is just that, if S+ isn't doing anything other than watching for the stroke button and passing along mouse messages, it's not actually using the CPU.
Sorry, but given that all of the core logic resides within the mouse hook callback (meaning, S+ doesn't forward an internal mouse event message to be handled elsewhere in code), changing the priority to Normal isn't something I'll add support for any time in the foreseeable future. You're more than welcome to manually change the priority as you wish, but it's just not something I will add as it can affect the reputation of S+ (StrokeIt handles priority how you've requested, and people with slower systems post in the SI forums about the lag when the system is under load).
|
|
|
|
Topic |
|
|
|