DisplayFusion RSS: How to find what prevents (keyboard) function from being applied

RE: How to find what prevents (keyboard) function from being applied

Binary Fortress Software — Wed, 09 Oct 2024 13:14:44 GMT

Thank you for the confirmation. I figured that was probably going to be the case.

RE: How to find what prevents (keyboard) function from being applied

Binary Fortress Software — Wed, 09 Oct 2024 13:03:31 GMT

Yeah we were able to reproduce the same thing after updating to 24H2, seems like Windows has it reserved now. There isn't much we can do there unfortunately

RE: How to find what prevents (keyboard) function from being applied

Binary Fortress Software — Fri, 04 Oct 2024 18:33:21 GMT

Hi Owen, thank you for that. However, I was unable to find any hotkey associated with that key combination. It is awfully coincidental that it popped up immediately after installing Windows 11 latest version.

Windows 11 24H2 allegedly has no new hotkeys. Is there any way to tell from the DF logs what caused it to be unable to apply a specific sequence? I'm not against changing my key sequences at all. It is just strange that there seems to be no explanation for it. I had tried some other hotkey listing tools for Windows as well, none of which listed that sequence. Interestingly, ALT+WIN+X works just fine.

What I can say is that the behavior is fairly consistent between DF versions 10.1.2 and 11 Beta 7. I don't have another operating system to test things out on at the moment. Perhaps I can test at a later time on another system to see if I can narrow it down.

RE: How to find what prevents (keyboard) function from being applied

Binary Fortress Software — Fri, 04 Oct 2024 13:34:30 GMT

I haven't used it personally, but I've heard Spy++ can find it for you. There's a write up on it here: https://www.tomshardware.com/software/windows/how-to-resolve-hotkey-conflicts-in-windows

RE: How to find what prevents (keyboard) function from being applied

Binary Fortress Software — Thu, 03 Oct 2024 18:09:27 GMT

This is new to Win11 24H2 because it worked yesterday on 23H2 (before I took the update).

How to find what prevents (keyboard) function from being applied

Binary Fortress Software — Thu, 03 Oct 2024 17:03:57 GMT

Running Windows 11 24H2 x54 and DF 10.1.2. My function to move a window to the next monitor has suddenly stopped working. I had it assigned to

CTRL+WIN+X

.

I changed the assignment to

CTRL+WIN+H

as a test. This worked. But when I tried to assign it back to

CTRL+WIN+X

I was presented with an error I've never encountered before (see attachment).

Is there any way to figure out what is preventing me from using the combination I've always used?