Quote:
Well, I did not ask for your 'opinion' about the etiquette I should be adhering too. Rather I ask a question of how to do some particular coding. And if you will read the question fully you will see my intentions are to turn it off after turning it on if the user's was turned off in the first place. And that includes if the app loses focus.
Dave is right: it's not a matter of "etiquette I should be adhering too", it's not even just a common courtesy - it's a deliberate attempt to undermine how the user (or the group policy administrator) has specifically told Windows to behave - and neither you nor I know
why they have been disabled, or who by.
It may be that the device is running as a Kiosk and shortcut keys may pose a security risk, it maybe that the user is too dumb to remember how to use them! Nobody knows...
Changing system wide settings is always a bad idea, even if you intend to restore the original setti8ng when you are finished: it's like using TAB and ENTER to change the colours in your app: it makes it harder for the user to use your application in the context of the whole machine - similar to the way Refresh is F5 in 90% of apps, but F9 in Outlook; you have to specifically remember the exception which makes the app harder to use.
Instead if you really must have shortcuts, override
Form.ProcessCmdKey[
^] and handle them yourself. No guarantees the user will go along with that though!
Quote:
Downgrade me all you want, I don't really care because I will be going somewhere else for my questions from now on.
Sorry to hear that. Do you need assistance in closing your account?
Submit an article or tip