AutoHotkey Community

[Stefan]

FYI and maybe suggestion if this is from interrest for more users too.


Just playing around with creating folders with current year and mont,
iam missing the build in variables

A_decade / %A_YD%
to get '04' from '2004'


and BTW maybe
A_century / %A_YC%
to get '20' from '2004'
too
_________________
Stefan

This post was created with the kindly help of http://dict.leo.org/ and remember: “Allways look on the bright side of Life”

[Chris]

I'm not ruling this out, but for now I'd like to avoid adding variables for rarely used things when there's a way to derive them from existing variables. In this case:

StringLeft, Century, A_YYYY, 2
StringRight, Decade, A_YYYY, 2

Thanks.

Edit: Fixed sample commands above.

[Stefan]

Not so nifty for a short script like

Send, {F7}
Send, Download_%A_mon%%A_century%

but your obove suggestion works, thanks very much for your help.

(I had smtg in mind like that "Trim" thing, but i have no experience with this (till now, i hope?) )

---------------------

Now i wanna use this
    StringTrimLeft, Century, A_YYYY, 2
    StringTrimRight, Decade, A_YYYY, 2

(and maybe other 'global' settings)

for all *.AHK scripts
and wanna write this in a "Main_Script.ahk".
(I tryed "The Auto-execute Section" of Autohotkey.ini)


Could this work ?
Can anyone pls give me an hint for what to search in the help for that issue ???

Thanks
_________________
Stefan

This post was created with the kindly help of http://dict.leo.org/ and remember: “Allways look on the bright side of Life”

[Chris]

[Stefan]

[Chris]

[Stefan]

[Chris]

Thanks; I don't think I want to have any special meaning assigned to the AutoHotkey.ini file, since it is just a script whose name happens to end in .ini. But do note that the default include file could include other files. In other words, even though only one default include will be possible, you can have any number of #Include statements inside that file.

Also, I'm thinking it might be better to have the default include file in %A_ScriptDir%. This makes things more flexible because you could then have separate folders each with their own default include file. However, it also prevents subfolders from easily using the same default include file, so in that respect it is worse. Some more consideration of these issues will be needed before implementation.

Thanks for your suggestions.

[jack]

it sounds as though you want a search path: read the one in the same folder; if it's not there, use the master copy.

but then you have the problem of turning it off!


jack
This is a REPEATABLE error situation

[Chris]

Yes, very good point. But maybe it's better just to keep it simple: If the script's own folder has a "#include_default.ahk" file in it, it gets included. Otherwise it doesn't.

As for turning it off, if no "master file" is supported, maybe there doesn't need to be a way. Any script that doesn't need the file included can be put into a sub-folder instead.

Another option is to store the configuration settings in a new/standard ini file somewhere, or in the registry. This would allow options such as "none (default)", "master only", "master and working directory", "working directory only", etc.

I don't currently consider this a super-high priority. But if you or anyone else has a craving for it in the near-term, please let me know.

[jack]

not me. i don't need this one.

jack
eleven dimensions ought to be enough for anybody

[Stefan]

[Chris]

[Guest]

[jonny]

Whoa, whoa, whoa. I just saw this thread now, and I for one don't like this idea. Maybe making AutoHotkey.ini into a global settings file (not a script) wouldn't be so bad, but going any further than that is just bloat in my opinion. It's trivial to simply make your own default.ahk and then put #Include default.ahk in the scripts you want affected. That's one line of code, 21 characters. Taking the step to have to include something to not include this default script would deter more people than it would help, I think.