Processing Ajax...

Title
Close Dialog

Message

Confirm
Close Dialog

Confirm
Close Dialog

Confirm
Close Dialog

User Image
Peter DeSimone
10 discussion posts
After the update, I got this message.

The Key Combination bind failed:
• Move Window to Center of Monitor and Size to 75% 'Ctrl + Win + S'
The Key Combination is already in use. There are a few reasons why this can happen:
- The Key Combination is already assigned elsewhere in this application
- Another application is already using this Key Combination
- A built-in Windows function is using this Key Combination

Please edit or remove the Key Combination in the settings.

Suggestion: when a dialog like this appears, can you provide a link to get the appropriate screen. I tried looking through the settings and I don't see anything about Key Combinations.

I read a few others posts. Is there anything new?
May 1, 2018 (modified May 1, 2018)  • #1
Alan Wade's profile on WallpaperFusion.com
Right click on the DF taskbar and choose Settings. Second tab down - Functions is where you will find the Key Combinations. Double click on any you wish to edit.
May 2, 2018 (modified May 2, 2018)  • #2
User Image
Gerard Burke
1 discussion post
This resolved it for me as well.

Thanks!
May 3, 2018  • #3
User Image
Lowell2
17 discussion posts
We've deployed DisplayFusion to many customers and as this Windows update rolls out we're going to start getting a ton of tickets complaining about this. This should have been rolled out as a pre-emptive fix in DisplayFusion; remove the shortcut. Because yes, we can deploy a registry hack fix but now that has to stay in place because it's a user-profile-specific fix and this setting is for some reason a default/built-in shortcut when DisplayFusion is installed.

Could you roll out a fix that disables this keyboard shortcut in a DisplayFusion update? It seems smarter to just disable that in the app than have us have to explain to potentially hundreds of users (some multiple profiles on one computer).
May 4, 2018  • #4
User Image
Lowell2
17 discussion posts
BTW, after a bunch of exporting/differencing/searching/comparing this seems to be the registry key that needs to be set to disable that keyboard shortcut:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Binary Fortress Software\DisplayFusion\HotKeys]
"HotKey_CentreWindowSize"=""

(For reference, the original key by default is below)

"HotKey_CentreWindowSize"="CTRL;WIN;83"
May 4, 2018 (modified May 4, 2018)  • #5
Alan Wade's profile on WallpaperFusion.com
Quote:
BTW, after a bunch of exporting/differencing/searching/comparing this seems to be the registry key that needs to be set to disable that keyboard shortcut:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Binary Fortress Software\DisplayFusion\HotKeys]
"HotKey_CentreWindowSize"=""

(For reference, the original key by default is below)

"HotKey_CentreWindowSize"="CTRL;WIN;83"


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.
May 6, 2018  • #6
User Image
Lowell2
17 discussion posts
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.
May 7, 2018  • #7
User Image
FullCourtPress
1 discussion post
Quote:
BTW, after a bunch of exporting/differencing/searching/comparing this seems to be the registry key that needs to be set to disable that keyboard shortcut:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Binary Fortress Software\DisplayFusion\HotKeys]
"HotKey_CentreWindowSize"=""


I'm also a business IT admin. The first place I looked for this was in the otherwise impressive DisplayFusion Group Policy templates. Unfortunately, I didn't see anything about to configuring keyboard shortcuts, so I found it pretty quickly using ProcMon.exe.

Can we turn this problem into a feature request to add hotkey support to the group policy templates? Right now, I'm using this registry key as an "apply once" Group Policy Preference item, but some sort of hotkey mapper via the .admx file would be great. I can think of other situations where we would want to turn off some of the shortcuts that get accidentally pressed, generating support calls.

I'm also of the opinion that this shortcut should be disabled or changed by default in future builds, at least for computers running 1803 and up, but configuring it would be much more useful.
May 8, 2018  • #8
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Hey all, sorry for the delayed response on this. It's already disabled in the latest 9.2 Beta, and we're planning the final release of 9.2 for next week.

Regarding Group Policy templates, it would be pretty tricky to have a Group Policy setting for every single function in the Functions list. However, there are a couple of things that can help here:


Hopefully one of those two options will work for you!
May 8, 2018 (modified May 8, 2018)  • #9
User Image
Lowell2
17 discussion posts
Quote:
Hey all, sorry for the delayed response on this. It's already disabled in the latest 9.2 Beta, and we're planning the final release of 9.2 for next week.

Regarding Group Policy templates, it would be pretty tricky to have a Group Policy setting for every single function in the Functions list. However, there are a couple of things that can help here:


Hopefully one of those two options will work for you!


Awesome, thanks Keith both for the fix and the detailed information regarding group policy settings. If the first link doesn't work for anyone (as it doesn't for me) it's this, will try see if this works:

https://www.displayfusion.com/AdvancedSettings/#general_dontshowerrormessagesforhotkeybindfailures
May 8, 2018 (modified May 8, 2018)  • #10
Keith Lammers (BFS)'s profile on WallpaperFusion.com
No worries! I'm open to more feedback if needed, so definitely let me know if you still have any trouble.

Thanks!
May 8, 2018  • #11
Keith Lammers (BFS)'s profile on WallpaperFusion.com
Haha yeah, I pasted the wrong text at first, I've edited my post as well :)
May 8, 2018  • #12
Subscribe to this discussion topic using RSS
Was this helpful?  Login to Vote(3)  Login to Vote(1)