@ScriptDir

[MasonMill]

Where is the file containing @ScriptDir?

[Melba23]

MasonMill,

There is no file - @ScriptDir is a macro generated at runtime.

M23

[MasonMill]

I should have been more clear. When you use iniwrite it writes to a file you designate is what i understand it to do. Where does that file get put? Like for example:

IniWrite(@ScriptDir&"\Set.ini","SetFull","Y1","0")

[Melba23]

MasonMill,

The file will be created in the same folder as the script - that is what the macro @ScriptDir holds.

So if your script was in "C:\MasonMill\Scripts", you would be creating the file "C:\MasonMill\Scripts\Set.ini".

All clear?

M23

[MasonMill]

Oh i see it now. The script was on my desktop so it just puts it on my desktop, or where ever the script is. Thanks!

[ShawnW]

except in this case you don't really need to put that. If you just did

IniWrite("Set.ini","SetFull","Y1","0")

I think it would look in the path local to the script by default.

[Melba23]

ShawnW,

I think it would look in the path local to the script by default

Correct!

M23

[MvGulik]

whatever Edited February 7, 2011 by MvGulik

[Melba23]

MvGulik,

You learn something every day - or at least you should! Although in my defence - unless you specify otherwise, the working folder starts as the script folder.

Thanks.

M23

Edit: Altered text - se below.

Edited May 7, 2010 by Melba23

[Richard Robertson]

By default, most processes use their folder as the working directory at start time. However, many things can chance the working directory, including a file save dialog.

[Melba23]

Richard Robertson,

2 things in 2 minutes - not sure my aged brain can learn this fast!

Previous post edited - thanks.

M23

[jaenster]

MasonMill,

The file will be created in the same folder as the script - that is what the macro @ScriptDir holds.

So if your script was in "C:\MasonMill\Scripts", you would be creating the file "C:\MasonMill\Scripts\Set.ini".

All clear?

M23

only when you run that script mainly (Not as an include)

But what he said is true.

If ya run your program, from c:\ , and you use @scriptdir&"\hi.ini" it is in c:\hi.ini

If you ever gonna work with includes, it gonna work a bit harder, It is the current map where you work with

Ever saw the command run() ?

if you do for example, run("c:\dir\Myprogram.exe","c:\","")

Now his workdir is in c:\. This means that @scriptdir = c:\

Someone correct me when i am wrong, didn't used autoit for a long time

[Richard Robertson]

only when you run that script mainly (Not as an include)

But what he said is true.

If ya run your program, from c:\ , and you use @scriptdir&"\hi.ini" it is in c:\hi.ini

If you ever gonna work with includes, it gonna work a bit harder, It is the current map where you work with

Ever saw the command run() ?

if you do for example, run("c:\dir\Myprogram.exe","c:\","")

Now his workdir is in c:\. This means that @scriptdir = c:\

Someone correct me when i am wrong, didn't used autoit for a long time

No, @ScriptDir in your example would still be "C:\dir". @WorkingDir would be "C:\".

[MHz]

The working directory can be @ScriptDir in case of double click in explorer but starting a script from the registry, a command prompt, a shortcut etc can pass a working directory other the @ScriptDir and you need to accept that and use it.

Many installed applications use a passed working directory to access files in the working directory. To have similar behavior for your script, then store the working directory at initial start of script and use that to access files. For some of the examples given, the working directory can be passed to the script and a ini file can be used in the specified working directory.

For example:

; store initial working directory at top of script
Global Const $STARTWORKINGDIR = @WorkingDir

; you can change the working directory of the script but $STARTWORKINGDIR is same
FileChangeDir('Any Dir change will not affect $STARTWORKINGDIR')

; use $STARTWORKINGDIR to access files
IniWrite($STARTWORKINGDIR & '\test1.tmp.ini', 'section', 'key', 'value')

You could use @ScriptDir instead of $STARTWORKINGDIR used above but you lose the option of using the passed working directory.