Custom Query

Hiho Devs,

I have a feature request regarding the infamous / feared / well known "AutoIt Error: Line xxx, Error: Array variable has incorrect number of subscripts or subscript dimension range exceeded."

Would it be possible to add not only the Line number (which is esp. in large scripts quite hard to track because of comments etc.) but also the failing script line itself below the custom error message for Info? That would make it much easier to debug

Regards

Despite the specifications on the wiki, I have tested code like the following and discovered that the left and right control and alt buttons do not release properly. There are a couple discussions of this problem on the forums, but no one seems to have a solution or workaround for it.

Send("{LCTRL DOWN}"); Left control is held down
Sleep(1000)
Send("1"); etc etc.
MouseClick("left")
Send("{LCTRL UP}"); Left control does NOT release

I just recently upgraded from AutoIt 3.3.0.0 to 3.3.6.1 (yes, I know I was behind the times). The application I had been working on runs as an interactive service running under the SYSTEM account. Part of the script is to log off the currently logged on user then perform other actions after the logoff is complete. When I ran the script that was compiled under 3.3.0.0, the script survived the logoff event just fine, however, when compiled with 3.3.6.1, the script would terminate at user logoff.

I had read several forum posts regarding the WM_QUERYENDSESSION mesasage that is sent to each top level window during logoff and had incorporated my own GUIRegisterMsg function to try to compensate for this, but the function that handled this event only delayed the inevitable termination of the script.

I have not read anything in any of the changelog entries that refer to the changing of this behavior on purpose, so I belive this to be a bug.

To test this, the following code can be compiled with any version of AutoIt higher than 3.3.0.0.

#include <GUIConstantsEx.au3>
$Form1 = GUICreate("AutoIt Version: " & @AutoItVersion, 415, 165, 192, 124)
$Label1 = GUICtrlCreateLabel("This script is running in the context of the account: " & @UserName, 32, 64, 328, 17)
GUISetState(@SW_SHOW)

While 1
	$nMsg = GUIGetMsg()
	Switch $nMsg
		Case $GUI_EVENT_CLOSE
			Exit
	EndSwitch
WEnd

The script does not need to be run as a service, as long as it runs under the SYSTEM account and running interactively with the logged on user; so scheduling the script to run using the AT command will work using the following command: AT 'time' /interactive 'Path to script'\'ScriptName'

Once the script launches, perform a logoff, then log back on to windows. You will notice that the script will have terminated. If the same script is compiled with version 3.3.0.0 and run interactively from the SYSTEM account, the GUI window will still be there waiting for you when you log back on.

I do have a workaround for this issue; I just compile the script using 3.3.0.0, but I would love for it to behave in this way in future versions and not be relegated to using a 2+ year old version.

Please note that I have tried this with every major version from 3.3.0.0 to 3.3.6.1 and version 3.3.0.0 was the last version that was able to behave in this manner.