Forums list
New topics
Topics list
Search
Help
Login
Register

Messages 1 - 10 of 15
First | Prev. | 1 2 | Next | Last 

Topic: «[FIXED] After updating to AMM 8.14.6.x move to next monitor no longer working » on forum: Technical Support   Views: 1829
 
Lee Murawski
Registered user
 
Posts: 3
Joined: 30.11.2021
Posted: 30.11.2021 09:21:33
 
 
After updating to AMM 8.14.6.x, the WinKey + / (move to next monitor) has stopped working on 2 different PCs.

WinKey + Shift + / is still working.

I updated to WinKey + \, which also did not work.

Thanks,
Lee Murawski
 
Top
David Lomas
Advanced user
 
Posts: 377
Joined: 16.03.2006
Posted: 30.11.2021 16:13:10
 
 
I have this issue too—with a different key combination (Win+Shift+Alt+N). Move to previous monitor is working fine. I tried switching the key combinations round, and only the action 'Move to previous monitor' works, no matter what the shortcut.

AWM 8.14.6.1 on Windows 10 21H1.
 
Top
LKL
Registered user
 
Posts: 4
Joined: 26.11.2021
Posted: 30.11.2021 19:34:50
 
 
I reported this as well: https://www.actualtools.com/forum/read.php?FID=10&TID=5815
 
Top
Bogdan Polishchuk
Administrator
 
Posts: 3810
Joined: 04.04.2012
Posted: 01.12.2021 06:57:37
 
 
Hello, everyone

Thank you for contacting us.

I was unable to reproduce the problem.

Does the "Move to next monitor" hotkey not work on each of your monitors or only on particular ones?

Could you see whether the Move to monitor extra title button and extra window menu item work? You can enable them here: AMM/AWM configuration module > Window Settings > Default Settings > Title Buttons/Window Menu > Move to monitor (in case of title buttons the standard one with the status <next>).

Also please specify the values of the "Change the size of text..." option in the standard Windows display settings for each monitor.

Could you also send us your AMM/AWM configuration files using the Send to Tech Support tool (AMM/AWM configuration module > Tools > Configuration > Send to Tech Support)? Add a link to this topic in the email.


Best regards.
 
Top
Lee Murawski
Registered user
 
Posts: 3
Joined: 30.11.2021
Posted: 01.12.2021 08:47:56
 
 
The hotkey does not work from either monitor for both PCs that I am experiencing this issue from.  One PC is Windows 11 (emailed config), the other is Windows 10.

WinKey + Shift + / does work.

Move to Monitor button in the title bar also works. Right-click title bar and Move to monitor # works.

Windows 11 - 2 screens 2560 x 1440 and 1920 x 1080 - Scale (Change the size of text) is 100% for both screens.
Windows 10 - 2 screens both 1920 x 1080 - Will provide configuration tomorrow.
 
Top
David Lomas
Advanced user
 
Posts: 377
Joined: 16.03.2006
Posted: 01.12.2021 16:18:38
 
 
For me (Windows 10, display 100%), the Next hotkey _only_ works when the titlebar button 'Move to monitor <next>' is enabled. When the titlebar button is disabled again, the hotkey stops working. I will leave the button enabled for now, in order to have the hotkey work. This might be a workaround for others too?

The 'Move to previous' hotkey is unaffected by this.

Config file incoming.
 
Top
Lee Murawski
Registered user
 
Posts: 3
Joined: 30.11.2021
Posted: 01.12.2021 21:54:48
 
 
I have tested the same, when the titlebar button 'Move to monitor <next>' is enabled, the hotkey is working.
 
Top
LKL
Registered user
 
Posts: 4
Joined: 26.11.2021
Posted: 02.12.2021 02:00:10
 
 
Quote
David Lomas wrote:
the Next hotkey _only_ works when the titlebar button 'Move to monitor <next>' is enabled. When the titlebar button is disabled again, the hotkey stops working. I will leave the button enabled for now, in order to have the hotkey work. This might be a workaround for others too?

This worked for me, thanks!
 
Top
Alex Fadeyev
Administrator

Moderator
 
Posts: 1406
Joined: 30.09.2005
Posted: 02.12.2021 03:38:13
 
 
Another workaround - to disable both the Move to Monitor title button and the Move to Monitor window menu command. The issue appears only when the title button is disabled and the menu command is enabled.
 
Top
Bogdan Polishchuk
Administrator
 
Posts: 3810
Joined: 04.04.2012
Posted: 04.12.2021 09:04:10
 
 
Hi, everyone

We'll try to fix this problem soon and will post here when the fix is available. For now you can use one of the two mentioned workarounds.


Best regards.
 
Top

Messages 1 - 10 of 15
First | Prev. | 1 2 | Next | Last 

User(s) reading this topic
Number of guests: 1, registered members: 0, in total hidden: 0


Forums list
New topics
Topics list
Search
Help
Login
Register