>Yes, I thought of that. But again, I always rule out mucking with system-wide settings.

For once I agree with both of you. As the old saying goes, if you watnt to do something wrong, do it right.

So if it's a system-wide setting and you don't have any other option but to change it temporarily, double and triple check that you've restored it before leaving, no matter how and why you left. Wrap it in a class, with the revert behavior in the .destroy(), make it a local instance in the caller, make sure it neatly does its thing when an error happens, or when app loses focus. In case of a C0005... find a way to say you're sorry.

>>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 ;-)