Code: Select all
send {lwin down}{+}{lwin up}
Code: Select all
send {lwin down}{+}{lwin up}
Code: Select all
F3::
SoundBeep, 1500
Run, %A_WinDir%\System32\Magnify.exe
Return
When I run Magnifier directly through its .exe file in Autohotkey, the mouse buttons often stop working when the screen is magnified. This does not happen when Magnifier is run with the Win + + key combination by the user himself.mikeyww wrote: ↑04 May 2021, 07:23Code: Select all
F3:: SoundBeep, 1500 Run, %A_WinDir%\System32\Magnify.exe Return
Whether or not it’s the issue with the magnifier program, the issue you are describing in general could be because you didn’t identify the working directory in the second parameter of the Run command. For the magnifier, it would be:Alexander2 wrote: ↑05 May 2021, 11:13I have long ago noticed that certain programs behave differently when they are run through AutoHotkey. The system even assigns them separate icons on the taskbar if other instances of the same programs are running.
Code: Select all
Run, %A_WinDir%\System32\Magnify.exe, %A_WinDir%\System32
UAC is disabled on my computer. And AutoHotkey is always run in the Administrator mode.mikeyww wrote: ↑06 May 2021, 06:39Your description provides the feel of an admin or UAC issue at hand. Would have a look at the following guide.
https://www.autohotkey.com/docs/FAQ.htm#uac
I have tried using this command, but the mouse buttons still stop working inside certain programs when the screen is magnified. (For example, the mouse buttons stop working on Kaspersky Internet Security, although they work on the Desktop when the screen is magnified. This does not happen when Magnifier is launched manually rather than through AutoHotkey.)boiler wrote: Whether or not it’s the issue with the magnifier program, the issue you are describing in general could be because you didn’t identify the working directory in the second parameter of the Run command. For the magnifier, it would be:Code: Select all
Run, %A_WinDir%\System32\Magnify.exe, %A_WinDir%\System32
Code: Select all
~F3::
Send {LWin down}{NumpadAdd}{LWin up}
Return
When I run Magnifier manually, the mouse buttons always work when the screen is magnified.I'm guessing it's not AutoHotkey that's the culprit. You would likely have the same result if you ran the file manually from File Explorer by double-clicking on it from its directory (typically C:\Windows\System32).
I need the Administrator mode because the script includes a command to close Task Manager, which requires the Administrator mode. But before I began using the script in this mode, I remember that programs had similarly behaved differently when run through AutoHotkey in the non-Administrator mode.Since you are running AHK in admin mode, try it without admin mode.
Thank you. The command Send {LWin down}{NumpadAdd}{LWin up} starts Magnifier normally, and the mouse buttons work now.Instead of {+} try NumPadAdd
Manually with the keyboard shortcut or manually by double-clicking the file in File Explorer like I described? (or both?)Alexander2 wrote: ↑ When I run Magnifier manually, the mouse buttons always work when the screen is magnified.
I have tested both methods, and in both instances, the mouse buttons work after magnification.boiler wrote: ↑07 May 2021, 14:22Manually with the keyboard shortcut or manually by double-clicking the file in File Explorer like I described? (or both?)Alexander2 wrote: ↑ When I run Magnifier manually, the mouse buttons always work when the screen is magnified.
I just tried this, and I did not get a file recovery message. I tried it both with:Alexander2 wrote: ↑ On your computers, when you open a .docx file with the Run command and Microsoft Word is automatically launched to open the file, do you get the file recovery message when you subsequently manually open another .docx file while the previous .docx file is still open?
Code: Select all
Run, myfilepath.docx
Code: Select all
Run, winword.exe myfilepath.docx
Then it seems that the system reacts differently to AutoHotkey only on my computer when the Run command is used in the case of Magnifier and Microsoft Word. Therefore, I will have to use the {lwin down}{numpadadd}{lwin up} command instead of "Run" to start Magnifier for it to work normally.I just tried this, and I did not get a file recovery message.
Users browsing this forum: Ragnar and 345 guests