-------------------
From docs/commands/Click.htm
Code:
48c48
< <p><strong>Mouse Wheel</strong> (this has no effect on Windows 9x): Specify WheelUp or WU to turn the wheel upward (away from you); specify WheelDown or WD to turn the wheel downward (toward you). In v1.0.48+, WheelLeft (or WL) or WheelRight (or WR) may also be specified (but they have no effect on older operating systems older than Windows Vista). For <em>ClickCount</em> (below), specify the number of notches to turn the wheel. However, some applications do not obey a <em>ClickCount</em> higher than 1 for the mouse wheel. For them, use a <a href="Loop.htm">Loop</a> such as the following:</p>
---
> <p><strong>Mouse Wheel</strong>: Specify WheelUp or WU to turn the wheel upward (away from you); specify WheelDown or WD to turn the wheel downward (toward you). In v1.0.48+, WheelLeft (or WL) or WheelRight (or WR) may also be specified (but they have no effect on older operating systems older than Windows Vista). For <em>ClickCount</em> (below), specify the number of notches to turn the wheel. However, some applications do not obey a <em>ClickCount</em> higher than 1 for the mouse wheel. For them, use a <a href="Loop.htm">Loop</a> such as the following:</p>
-------------------
From docs/commands/Drive.htm
Code:
20c20
< Lock, Drive</strong>: Prevents a drive's eject feature from working. For example: "Drive, Lock, D:". Most drives cannot be "locked open". However, locking the drive while it is open will probably result in it becoming locked the moment it is closed. This command has no effect on drives that do not support locking (such as most read-only drives), nor is it likely to work on non-IDE drives on Windows 95/98/Me. If a drive is locked by a script and that script exits, the drive will stay locked until another script or program unlocks it, or the system is restarted. If the specified drive does not exist or does not support the locking feature, ErrorLevel is set to 1. Otherwise, it is set to 0.</p>
---
> Lock, Drive</strong>: Prevents a drive's eject feature from working. For example: "Drive, Lock, D:". Most drives cannot be "locked open". However, locking the drive while it is open will probably result in it becoming locked the moment it is closed. This command has no effect on drives that do not support locking (such as most read-only drives). If a drive is locked by a script and that script exits, the drive will stay locked until another script or program unlocks it, or the system is restarted. If the specified drive does not exist or does not support the locking feature, ErrorLevel is set to 1. Otherwise, it is set to 0.</p>
-------------------
From docs/commands/Exit.htm
Code:
20c20
< <dd><p>An integer between -2147483648 and 2147483647 (can be an <a href="../Variables.htm#Expressions">expression</a>) that is returned to its caller when the script exits. This code is accessible to any program that spawned the script, such as another script (via RunWait) or a batch (.bat) file. If omitted, ExitCode defaults to zero. Zero is traditionally used to indicate success. Note: Windows 95 may be limited in how large ExitCode can be.</p></dd>
---
> <dd><p>An integer between -2147483648 and 2147483647 (can be an <a href="../Variables.htm#Expressions">expression</a>) that is returned to its caller when the script exits. This code is accessible to any program that spawned the script, such as another script (via RunWait) or a batch (.bat) file. If omitted, ExitCode defaults to zero. Zero is traditionally used to indicate success.</p></dd>
-------------------
From docs/commands/ExitApp.htm
Code:
20c20
< <dd><p>An integer between -2147483648 and 2147483647 (can be an <a href="../Variables.htm#Expressions">expression</a>) that is returned to its caller when the script exits. This code is accessible to any program that spawned the script, such as another script (via RunWait) or a batch (.bat) file. If omitted, ExitCode defaults to zero. Zero is traditionally used to indicate success. Note: Windows 95 may be limited in how large ExitCode can be.</p></dd>
---
> <dd><p>An integer between -2147483648 and 2147483647 (can be an <a href="../Variables.htm#Expressions">expression</a>) that is returned to its caller when the script exits. This code is accessible to any program that spawned the script, such as another script (via RunWait) or a batch (.bat) file. If omitted, ExitCode defaults to zero. Zero is traditionally used to indicate success.</p></dd>
-------------------
From docs/commands/FileSelectFolder.htm
Code:
35c35
< <p><strong>1</strong> (default): A button is provided that allows the user to create new folders. However, the button will not be present on Windows 95/98/NT.</p>
---
> <p><strong>1</strong> (default): A button is provided that allows the user to create new folders.</p>
-------------------
From docs/commands/FileSetTime.htm
Code:
51d50
< <p>Under Windows 95/98/ME, changing the timestamp of folders is not supported. Attempts to do so are ignored.</p>
-------------------
From docs/commands/GuiControls.htm
Code:
59c59
< <p>Although multi-line edit controls are limited to 64 KB of text on Windows 95/98/Me, they may have as much as 4 GB of text on Windows NT/2k/XP or later. As the user enters text, more memory is allocated as needed.</p>
---
> <p>Multi-line edit controls may have as much as 4 GB of text on Windows NT/2k/XP or later. As the user enters text, more memory is allocated as needed.</p>
92c92
< <p><span class="green">Range</span>: Sets the range to be something other than 0 to 100. After the word Range, specify the minimum, a dash, and maximum. For example, Range1-1000 would allow a number between 1 and 1000 to be selected; Range-50-50 would allow a number between -50 and 50; and Range-10--5 would allow a number between -10 and -5. The minimum and maximum may be swapped to cause the arrows to move in the opposite of their normal direction. The broadest allowable range is -2147483648-2147483647. However, Windows 95 and NT4 require Internet Explorer 5.0 or later to support a range broader than -32767-32767. Finally, if the buddy control is a <a href="#ListBox">ListBox</a>, the range defaults to 32767-0 for verticals and the inverse for horizontals (<a href="#Horz">Horz</a>).</p>
---
> <p><span class="green">Range</span>: Sets the range to be something other than 0 to 100. After the word Range, specify the minimum, a dash, and maximum. For example, Range1-1000 would allow a number between 1 and 1000 to be selected; Range-50-50 would allow a number between -50 and 50; and Range-10--5 would allow a number between -10 and -5. The minimum and maximum may be swapped to cause the arrows to move in the opposite of their normal direction. The broadest allowable range is -2147483648-2147483647. Finally, if the buddy control is a <a href="#ListBox">ListBox</a>, the range defaults to 32767-0 for verticals and the inverse for horizontals (<a href="#Horz">Horz</a>).</p>
107d106
< <p>Due to an OS bug, animated cursors scaled to a size greater than 90x90 on Windows 95/98/Me might crash the script.</p>
216d214
< <p>Windows 95 and NT4 require DLL versions at least as new as those distributed with Internet Explorer 3.0 to support DateTime controls.</p>
233d230
< <p>Windows 95 and NT4 require DLL versions at least as new as those distributed with Internet Explorer 3.0 to support MonthCal controls.</p>
258c255
< <p><span class="green">Buddy1</span> and <span class="green">Buddy2</span>: Specifies up to two existing controls to automatically reposition at the ends of the slider. Buddy1 is displayed at the left or top side (depending on whether the Vertical option is present). Buddy2 is displayed at the right or bottom side. After the word Buddy1 or Buddy2, specify the <a href="Gui.htm#var">variable name</a> of an existing control. For example, Buddy1MyTopText would assign the control whose variable name is MyTopText. Windows 95 and NT4 require Internet Explorer 3.0 or later to support this option.</p>
---
> <p><span class="green">Buddy1</span> and <span class="green">Buddy2</span>: Specifies up to two existing controls to automatically reposition at the ends of the slider. Buddy1 is displayed at the left or top side (depending on whether the Vertical option is present). Buddy2 is displayed at the right or bottom side. After the word Buddy1 or Buddy2, specify the <a href="Gui.htm#var">variable name</a> of an existing control. For example, Buddy1MyTopText would assign the control whose variable name is MyTopText.</p>
268c265
< <p><span class="green">ToolTip</span>: Creates a tooltip that reports the numeric position of the slider as the user is dragging it. To have the tooltip appear in a non-default position, specify one of the following instead: ToolTipLeft or ToolTipRight (for horizontal sliders); ToolTipTop or ToolTipBottom (for vertical sliders). Windows 95 and NT4 require Internet Explorer 3.0 or later to support this option.</p>
---
> <p><span class="green">ToolTip</span>: Creates a tooltip that reports the numeric position of the slider as the user is dragging it. To have the tooltip appear in a non-default position, specify one of the following instead: ToolTipLeft or ToolTipRight (for horizontal sliders); ToolTipTop or ToolTipBottom (for vertical sliders).</p>
282c279
< <p><span class="green">Range</span>: Sets the range to be something other than 0 to 100. After the word Range, specify the minimum, a dash, and maximum. For example, Range0-1000 would allow a numbers between 0 and 1000; Range-50-50 would allow numbers between -50 and 50; and Range-10--5 would allow numbers between -10 and -5. On Windows 95 and NT4, negative ranges and ranges beyond 65535 will not behave correctly unless Internet Explorer 3.0 or later is installed.</p>
---
> <p><span class="green">Range</span>: Sets the range to be something other than 0 to 100. After the word Range, specify the minimum, a dash, and maximum. For example, Range0-1000 would allow a numbers between 0 and 1000; Range-50-50 would allow numbers between -50 and 50; and Range-10--5 would allow numbers between -10 and -5.</p>
284c281
< <p><span class="green">Vertical</span>: Makes the bar rise or fall vertically rather than move along horizontally. Windows 95 and NT4 require Internet Explorer 3.0 or later to support this option.</p>
---
> <p><span class="green">Vertical</span>: Makes the bar rise or fall vertically rather than move along horizontally.</p>
-------------------
From docs/commands/index.htm
Code:
379c379
< <td>Waits for the user to type a string (not supported on Windows 9x: it does nothing).</td>
---
> <td>Waits for the user to type a string.</td>
531c531
< <td>Specifies a set of user credentials to use for all subsequent uses of <a href="Run.htm">Run</a> and <a href="Run.htm">RunWait</a>. Requires Windows 2000/XP or later.</td>
---
> <td>Specifies a set of user credentials to use for all subsequent uses of <a href="Run.htm">Run</a> and <a href="Run.htm">RunWait</a>.</td>
688c688
< <td>Creates a balloon message window near the tray icon. Requires Windows 2000/XP or later. </td>
---
> <td>Creates a balloon message window near the tray icon.</td>
-------------------
From docs/commands/ListView.htm
Code:
117c117
< <p><span class="green">Icon</span>: Specify the word Icon followed immediately by the number of the <a href="#IL">ImageList's</a> icon to display next to the column header's text. Specify -Icon (minus icon) to remove any existing icon. On Windows 95/NT4, column icons require the DLLs distributed with Internet Explorer 3.0 or later.</p>
---
> <p><span class="green">Icon</span>: Specify the word Icon followed immediately by the number of the <a href="#IL">ImageList's</a> icon to display next to the column header's text. Specify -Icon (minus icon) to remove any existing icon.</p>
208c208
< <a href="#IL_Add">IL_Add</a>(ImageListID, "shell32.dll", A_Index) <em>; Omits the DLL's path so that it works on Windows 9x too.</em>
---
> <a href="#IL_Add">IL_Add</a>(ImageListID, "shell32.dll", A_Index)
246d245
< <p>Windows 95 and NT4: If the system lacks version 4.70 or later of Comctl32.dll, Shell32.dll, and Shlwapi.dll -- which are distributed with various updates and applications such as Internet Explorer 3.0 or later -- ListViews are more limited and some features might not behave as expected.</p>
-------------------
From docs/commands/Menu.htm
Code:
60c60
< <p>There are some icons built into the operating system's DLLs and CPLs that might be useful. For example: <em>Menu, Tray, Icon, Shell32.dll, 174 <em>; Omits the DLL's path so that it works on Windows 9x too.</em></em></p>
---
> <p>There are some icons built into the operating system's DLLs and CPLs that might be useful. For example: <em>Menu, Tray, Icon, Shell32.dll, 174</em></p>
67c67
< <p><strong>Color, ColorValue [, Single]</strong>: Changes the background color of the menu to <em>ColorValue</em>, which is one of the 16 primary HTML color names or a 6-digit RGB color value (see <a href="../misc/Colors.htm">color chart</a>). Leave <em>ColorValue</em> blank (or specify the word Default) to restore the menu to its default color. If the word Single is not present as the next parameter, any submenus attached to this menu will also be changed in color. This command has no effect on Windows 95/NT.</p>
---
> <p><strong>Color, ColorValue [, Single]</strong>: Changes the background color of the menu to <em>ColorValue</em>, which is one of the 16 primary HTML color names or a 6-digit RGB color value (see <a href="../misc/Colors.htm">color chart</a>). Leave <em>ColorValue</em> blank (or specify the word Default) to restore the menu to its default color. If the word Single is not present as the next parameter, any submenus attached to this menu will also be changed in color.</p>
-------------------
From docs/commands/Process.htm
Code:
25c25
< <p><em>Param3</em> should be one of the following letters or words: L (or Low), B (or BelowNormal), N (or Normal), A (or AboveNormal), H (or High), R (or Realtime). Since BelowNormal and AboveNormal are not supported on Windows 95/98/Me/NT4, <em>normal</em> will be automatically substituted for them on those operating systems. Note: Any process not designed to run at Realtime priority might reduce system stability if set to that level.</p>
---
> <p><em>Param3</em> should be one of the following letters or words: L (or Low), B (or BelowNormal), N (or Normal), A (or AboveNormal), H (or High), R (or Realtime). Note: Any process not designed to run at Realtime priority might reduce system stability if set to that level.</p>
46d45
< <p> To work under Windows NT4, the Process command requires the file PSAPI.DLL, which is normally already present in the AutoHotkey installation directory (i.e. no extra installation steps should be needed even for NT). However, to use it from within a <a href="../Scripts.htm#ahk2exe">compiled script</a> on Windows NT4, include a copy of PSAPI.DLL in the same folder as the script or in one of the directories in the system's PATH (though some NT4 systems might already have the DLL).</p>
-------------------
From docs/commands/RegWrite.htm
Code:
41c41
< <p> Although no more than 64 KB of data can be written to REG_BINARY and REG_MULTI_SZ values, the other types are unlimited except under Windows 95/98/ME, which have a 64 KB limit for all types. If the 64 KB limit applies, data beyond that limit will not be written. In other words, only the first 64 KB of a very large string will be saved to the registry.</p>
---
> <p> Although no more than 64 KB of data can be written to REG_BINARY and REG_MULTI_SZ values, the other types are unlimited. If the 64 KB limit applies, data beyond that limit will not be written. In other words, only the first 64 KB of a very large string will be saved to the registry.</p>
43c43
< <p> When writing a REG_MULTI_SZ key, you must separate each component from the next with a linefeed character (`n). The last component may optionally end with a linefeed as well. No blank components are allowed. In other words, do not specify two linefeeds in a row (`n`n) because that will result in a shorter-than-expected value being written to the registry. Note: Windows 95 does not support the REG_MULTI_SZ value type.</p>
---
> <p> When writing a REG_MULTI_SZ key, you must separate each component from the next with a linefeed character (`n). The last component may optionally end with a linefeed as well. No blank components are allowed. In other words, do not specify two linefeeds in a row (`n`n) because that will result in a shorter-than-expected value being written to the registry.</p>
-------------------
From docs/commands/Shutdown.htm
Code:
64d63
< ; Windows 95/NT4: Since this function does not exist, the following call would have no effect.
-------------------
From docs/commands/SoundBeep.htm
Code:
29c29
< <p>On Windows 9x, the <em>Frequency</em> and <em>Duration</em> parameters are ignored. Instead, the system default sound event is played through the sound card. If the computer lacks a sound card, a standard beep is played through the PC speaker.</p>
---
> <p>If the computer lacks a sound card, a standard beep is played through the PC speaker.</p>
-------------------
From docs/commands/SysGet.htm
Code:
32,33c32,33
< <p><strong>MonitorCount</strong>: Retrieves the total number of monitors. Unlike SM_CMONITORS mentioned in the table below, <em>MonitorCount </em>includes all monitors, even those not being used as part of the desktop. On Windows 95/NT the count is always 1.</p>
< <p><strong>MonitorPrimary</strong>: Retrieves the number of the primary monitor, which will be 1 in a single-monitor system. On Windows 95/NT the primary monitor is always 1.</p>
---
> <p><strong>MonitorCount</strong>: Retrieves the total number of monitors. Unlike SM_CMONITORS mentioned in the table below, <em>MonitorCount </em>includes all monitors, even those not being used as part of the desktop.</p>
> <p><strong>MonitorPrimary</strong>: Retrieves the number of the primary monitor, which will be 1 in a single-monitor system.</p>
50c50
< <td>SM_CMONITORS: Number of display monitors on the desktop (not including "non-display pseudo-monitors"). <B>Windows 95/NT: </B>The retrieved value is always 0.</TD>
---
> <td>SM_CMONITORS: Number of display monitors on the desktop (not including "non-display pseudo-monitors").</TD>
91c91
< the virtual screen. <B>Windows NT, Windows 95: </B>The retrieved value is always 0.</TD>
---
> the virtual screen.</TD>
99c99
< <td>SM_MOUSEWHEELPRESENT: Nonzero if a mouse with a wheel is installed; zero otherwise. <B>Windows 95: </B>The retrieved value is always 0.</TD>
---
> <td>SM_MOUSEWHEELPRESENT: Nonzero if a mouse with a wheel is installed; zero otherwise.</TD>
110c110
< session is remotely controlled; zero otherwise. <B>Windows 2000/NT, Windows Me/98/95: </B>The retrieved value is always 0.</TD>
---
> session is remotely controlled; zero otherwise.</TD>
118c118
< is not necessarily the physical console. <B>Windows NT 4.0 SP3 and earlier, Windows Me/98/95: </B>The retrieved value is always 0.</TD>
---
> is not necessarily the physical console.</TD>
130c130
< SM_SHUTTINGDOWN: Nonzero if the current session is shutting down; zero otherwise. <B>Windows 2000/NT, Windows Me/98/95: </B>The retrieved value is always 0.</TD>
---
> SM_SHUTTINGDOWN: Nonzero if the current session is shutting down; zero otherwise. <B>Windows 2000/NT: </B>The retrieved value is always 0.</TD>
141c141
< and height of the virtual screen. <B>Windows NT, Windows 95: </B>The retrieved value is always 0.</TD>
---
> and height of the virtual screen.</TD>
188c188
< <td>SM_CXFOCUSBORDER, SM_CYFOCUSBORDER: Width (in pixels) of the left and right edges and the height of the top and bottom edges of a control's focus rectangle. <B>Windows 2000/NT, Windows Me/98/95: </B>The retrieved value is always 0.</TD>
---
> <td>SM_CXFOCUSBORDER, SM_CYFOCUSBORDER: Width (in pixels) of the left and right edges and the height of the top and bottom edges of a control's focus rectangle. <B>Windows 2000/NT:</B> The retrieved value is always 0.</TD>
260c260
< <td> SM_DBCSENABLED: Nonzero if User32.dll supports DBCS; zero otherwise. <B>Windows Me/98/95: </B>Nonzero if the double-byte character-set (DBCS) version of User.exe is installed; zero otherwise.</TD>
---
> <td> SM_DBCSENABLED: Nonzero if User32.dll supports DBCS; zero otherwise.</TD>
268c268
< <td> SM_IMMENABLED: Nonzero if Input Method Manager/Input Method Editor features are enabled; zero otherwise. <B>Windows NT, Windows Me/98/95: </B>The retrieved value is always 0.
---
> <td> SM_IMMENABLED: Nonzero if Input Method Manager/Input Method Editor features are enabled; zero otherwise.
293c293
< <td>SM_SAMEDISPLAYFORMAT: Nonzero if all the display monitors have the same color format, zero otherwise. Note that two displays can have the same bit depth, but different color formats. For example, the red, green, and blue pixels can be encoded with different numbers of bits, or those bits can be located in different places in a pixel's color value. <B>Windows NT, Windows 95: </B>The retrieved value is always 0.</TD>
---
> <td>SM_SAMEDISPLAYFORMAT: Nonzero if all the display monitors have the same color format, zero otherwise. Note that two displays can have the same bit depth, but different color formats. For example, the red, green, and blue pixels can be encoded with different numbers of bits, or those bits can be located in different places in a pixel's color value. </TD>
297c297
< <td>SM_SLOWMACHINE: Always zero on Windows NT/2000/XP or later. Nonzero on Windows 95/98/ME only if the computer has at least one of: a 386 processor, less than 6M of RAM, or a videocard that claims to be slow.</TD>
---
> <td>SM_SLOWMACHINE: Always zero on Windows NT/2000/XP or later.</TD>
-------------------
From docs/commands/TrayTip.htm
Code:
13c13
< <p>Creates a balloon message window near the tray icon. Requires Windows 2000/XP or later.</p>
---
> <p>Creates a balloon message window near the tray icon.</p>
45d44
< <p> TrayTip requires Windows 2000/XP or later. On Windows 9x/NT, the command does nothing.</p>
-------------------
From docs/commands/TreeView.htm
Code:
53,56c53
< <p><strong>HScroll</strong>: Specify -HScroll (minus HScroll) to disable horizontal scrolling in the control (in addition, the control will not display any horizontal scroll bar). On operating systems older than Windows 2000/Me, this option has no effect unless the system has
<
<
< Comctl32.dll 5.8 or greater (distributed with applications such as Internet Explorer 5 or later).</p>
---
> <p><strong>HScroll</strong>: Specify -HScroll (minus HScroll) to disable horizontal scrolling in the control (in addition, the control will not display any horizontal scroll bar)..</p>
60c57
< <a href="ListView.htm#IL_Add">IL_Add</a>(ImageListID, "shell32.dll", A_Index) <em>; Omits the DLL's path so that it works on Windows 9x too.</em>
---
> <a href="ListView.htm#IL_Add">IL_Add</a>(ImageListID, "shell32.dll", A_Index)
166d162
< <p>Windows 95 and NT4: If the system lacks version 4.70 or later of Comctl32.dll, Shell32.dll, and Shlwapi.dll -- which are distributed with various updates and applications such as Internet Explorer 3.0 or later -- TreeViews are more limited and some features might not behave as expected.</p>
186c182
< Loop 5 <em>; Below omits the DLL's path so that it works on Windows 9x too:</em>
---
> Loop 5
-------------------
From docs/commands/WinGetText.htm
Code:
44d43
< <p>Windows 95/98/ME may be limited to 64 KB for some text elements of certain windows.</p>
-------------------
From docs/commands/WinSet.htm
Code:
46c46
< <p><a href="../misc/ErrorLevel.htm">ErrorLevel</a> is set to 1 upon failure and 0 upon success. Failure occurs if the target window is not found or the style is not allowed to be applied (which happens more often on Windows 9x).</p>
---
> <p><a href="../misc/ErrorLevel.htm">ErrorLevel</a> is set to 1 upon failure and 0 upon success. Failure occurs if the target window is not found or the style is not allowed to be applied.</p>
65d64
< <li>They have no effect on Windows 9x and NT4.</li>
84c83
< <p>Makes all pixels of the chosen color invisible inside the target window, which allows the contents of the window behind it to show through (has no effect on Windows 9x and NT4). If the user clicks on an invisible pixel, the click will "fall through" to the window behind it. Specify for <em>Color</em> a color name or RGB value (see the <a href="../misc/Colors.htm">color chart</a> for guidance, or use <a href="PixelGetColor.htm">PixelGetColor</a> in its RGB mode). To additionally make the visible part of the window partially transparent, append a space (not a comma) followed by the transparency level (0-255). For example: <em>WinSet, TransColor, EEAA99 150, WinTitle</em></p>
---
> <p>Makes all pixels of the chosen color invisible inside the target window, which allows the contents of the window behind it to show through. If the user clicks on an invisible pixel, the click will "fall through" to the window behind it. Specify for <em>Color</em> a color name or RGB value (see the <a href="../misc/Colors.htm">color chart</a> for guidance, or use <a href="PixelGetColor.htm">PixelGetColor</a> in its RGB mode). To additionally make the visible part of the window partially transparent, append a space (not a comma) followed by the transparency level (0-255). For example: <em>WinSet, TransColor, EEAA99 150, WinTitle</em></p>
-------------------
From docs/commands/_IfWinActive.htm
Code:
43c43
< <p>When a mouse or keyboard hotkey is disabled via #IfWin, it performs its native function; that is, it passes through to the active window as though there is no such hotkey. There are two exceptions: 1) Windows 95/98/Me: pressing an IfWin-disabled hotkey has no effect (not even its native function); and 2) Joystick hotkeys: although #IfWin works, it never prevents other programs from seeing the press of a button.</p>
---
> <p>When a mouse or keyboard hotkey is disabled via #IfWin, it performs its native function; that is, it passes through to the active window as though there is no such hotkey. There is one exception: Joystick hotkeys: although #IfWin works, it never prevents other programs from seeing the press of a button.</p>
78,82c78
< <p>For performance reasons, #IfWin does not continuously monitor the activation or existence of the specified windows. Instead, it checks for a matching window only when you type a hotkey or hotstring. If a matching window is not present, your keystroke or mouse click is allowed to pass through to the active window unaltered (except on Windows 95/98/Me).</p>
< <p>Windows 95/98/Me: If the first variant of a hotkey has a $ prefix, all variants will be allowed to "send themselves". This provides a means for a hotkey to perform its native function rather than doing nothing at all. For example:</p>
< <pre>$^a::Send ^a <em>; The first variant must have a $ prefix to allow it to "send itself" on Windows 9x.</em>
< #IfWinActive ahk_class Notepad
< ^a::MsgBox You pressed Control-A while Notepad is active.</pre>
---
> <p>For performance reasons, #IfWin does not continuously monitor the activation or existence of the specified windows. Instead, it checks for a matching window only when you type a hotkey or hotstring. If a matching window is not present, your keystroke or mouse click is allowed to pass through to the active window unaltered.</p>
-------------------
From docs/commands/_UseHook.htm
Code:
28c28
< <p>Turning this directive ON is equivalent to using the <a href="../Hotkeys.htm#prefixdollar">$ prefix</a> in the definition of each affected hotkey. The exception to this is Windows 95/98/Me, upon which #UseHook is ignored (though the <a href="../Hotkeys.htm#prefixdollar">$ prefix</a> works in a limited fashion).</p>
---
> <p>Turning this directive ON is equivalent to using the <a href="../Hotkeys.htm#prefixdollar">$ prefix</a> in the definition of each affected hotkey.</p>
-------------------
From docs/commands/_WinActivateForce.htm
Code:
18d17
< <p>Windows 95 and NT will probably never need this setting since they are more permissive about allowing windows to be activated.</p>
Login
Register
FAQ
Search
