03-13-2021, 06:38 PM
(This post was last modified: 03-13-2021, 06:48 PM by Geoff Bacon.)
Mike
How about, when MSP starts or is reopened, asking the user whether a mouse is connected ? i.e. a single prompt but only if the option is enabled.
As mice are PnP, you would also have to detect if a mouse is subsequently connected/disconnected (but I suspect the API might have an event for this).
Alternatively ignore the option if there has been no mouse movement since the program started (possibly attempt to move mouse offscreen when MSP starts so that you get an early indication if user has a mouse).
(Might not be possible if the mouse is treated as a "touch" or vv)
Can the mouse be made transparent?
These are just thoughts and I've no idea how they could fit into your framework or whether they would introduce issues on other devices. It also adds more complexity to cover the inadequacies of the API and could cause you support problems as that changes.
Keep up the good work and Stay Safe
Geoff
How about, when MSP starts or is reopened, asking the user whether a mouse is connected ? i.e. a single prompt but only if the option is enabled.
As mice are PnP, you would also have to detect if a mouse is subsequently connected/disconnected (but I suspect the API might have an event for this).
Alternatively ignore the option if there has been no mouse movement since the program started (possibly attempt to move mouse offscreen when MSP starts so that you get an early indication if user has a mouse).
(Might not be possible if the mouse is treated as a "touch" or vv)
Can the mouse be made transparent?
These are just thoughts and I've no idea how they could fit into your framework or whether they would introduce issues on other devices. It also adds more complexity to cover the inadequacies of the API and could cause you support problems as that changes.
Keep up the good work and Stay Safe
Geoff
Samsung Galaxy Tab A6