With you on not changing Windows settings on the users machine willy-nilly. But an alternate approach might be to change the setting at start of the action, resetting when manual (mouse-pressed!) task is done. Existing danger opportunity of app erroring out while dragging without calling a reset function in error handler or machine blue-screening, sure, but might be handled with special reset code on next app start - even down to including a message about not resetting due to error and reccommending reset via app. ***Not*** saying I think this is a prudent way in general ;-)

>I said nothing about Microsoft. I'm talking about providing a good user experience. Changing Windows settings that affect every program is not a good idea. It causes confusion. Users will see their applications suddenly behaving differently and have no idea what happened or how to revert to the old experience.
>
>>You always repeat the Microsoft SOP. But you never inquire as to the possible unique scenarios under which such changes might be applicable, allowable, and/or useful.