Custom Query

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (145 - 147 of 3876)

Ticket Resolution Summary Owner Reporter
#472 No Bug @ScriptDir returns a slash (\) when script run from root congo (seanw@…
Description

In AutoIT v3.2.12.0, @ScriptDir is documented as NOT returning a trailing slash(\), however due to the Win API if a compiled script is run from a drive root (like an autorun DVD/CD) it does infact return a trailing backslash.

Easy to work around if you can't be 100% sure of where the app will be run:

	$myscript = @ScriptDir
	If StringRight($drive, 1) == "\" Then ;in root of a drive a trailing slash is returned by Windows!
		$t = StringSplit($drive, "\")
		$myscript = $t[1]
	EndIf

The documentation may need to be updated, or the macro modified

#2373 Fixed @ScriptDir returns trailing slash BinaryBrother@…
Description

@ScriptDir is returning a trailing slash for me, consistently, on the machine that I'm currently using.

The problem is either in functionality or documentation. The help documentation says that this Macro will NOT return a trailing slash.

Windows 7 x86 UAC Enabled -All Stock

Relevant forum thread: http://www.autoitscript.com/forum/topic/153104-scriptdir-returns-trailing-slash/

#2302 Rejected @ScriptLineNumber in compiled scripts Fulgor
Description

For testing I put several MsgBox(0,@ScriptLineNumber , "error x") in my script. But in the compiled file the ScriptLineNumber is always -1. I know here did not exist a linenumber, but for better find the error the compiled-script should also show the linenumber of the source-script.

Note: See TracQuery for help on using queries.