Quote:
Isnt it much simpler to disable or modify it in the settings?
You could end up with a lot of time spent writing various scripts everytime Microsoft decide to create a shortcut.
By that response it sounds like you folks don't deal much with businesses. Imagine an IT environment with 400+ computers and at least as many users, with a site-wide DisplayFusion license so it's on every computer. It's enough disruption at times to do something like the 1803 update, but now because a default keyboard shortcut you folks decided on now conflicts with what Microsoft uses, instead of removing it proactively for your customers you require that the customers individually, once for every profile on every computer they logon to, do the following:
1. Read the warning that you pop up (most end-users will be confused at what's happening as they don't remember what DisplayFusion is for, they just use it).
2. Click OK and the message disappears instead of just opening Settings, Functions for the user. Now they have to know to go to the system tray, right-click on the DisplayFusion icon, and click Settings.
3. Choose the Functions tab (nothing obvious like "keyboard shortcuts" for end-users to see).
4. Find the keyboard shortcut that's conflicting (if they can remember what it was).
5. Double-click on it or select and click Edit.
6. Click the Remove button.
7. Click OK.
8. Click OK again to exit Settings.
You're suggesting that this 8-step process the user has to know how to do is easier than you just removing the shortcut as a default one in your app?
Users will either just ignore the message and click OK to get on with their day or create a support ticket to have their IT people deal with it. So absolutely not, it's not "just easier" to have users go through all these steps, once per Windows profile on every computer they logon to that has DisplayFusion running.
