Report Help File Issues Here

[guinness]

This thread is to be used for reporting issues and/or code improvements for the AutoIt Help file only.

Up until now those that have posted have done so in a clear and concise manner, so lets keep it that way. If this starts to deviate in any way then I will be forced to adopt a similar approach as Trac does.

Issue with AutoIt:

For reporting an issue with AutoIt ensure you've isolated the problem in a small script that reproduces the error, assessed in the General Help and Support Forum that it's not a problem with poorly written code and then if none of those fix the problem post to Trac for an AutoIt Developer to assess the issue.

Edited December 28, 2011 by guinness

[GerrOrneq]

Help File Documentation - Reference to Windows 95

There is a reference to a fail situation in the Limits/Defaults section regarding values greater than 32768 in respect of WINTEXTBUFFER.

As support for Windows '98 is gone then I thought that reference to W '95 was also no longer needed in the help file.

http://www.autoitscript.com/autoit3/docs/appendix/LimitsDefaults.htm

Apologies if this is too minor an issue to mention.

Regards,

DeMo.

[guinness]

Thanks, I've removed for now until a Dev says otherwise.

[AZJIO]

guinness

StringRegExp.7z (5.4 KB) Ru

[guinness]

Thanks AZJIO, but honestly I can't read the file, the text I see aren't Russian characters but random characters.

[jchd]

@guinness

After applying "$ iconv -f cp1251 -t UTF-8 StringRegExp.txt > sre.txt" I obtained the file below (I added an UTF-8 BOM for safety).

I don't know if that was the right input encoding, but perhaps it will make some sense to you.

[JScript]

The text below could be applied in the variables of examples too!

Variable Names
The first set of characters after the dollar sign (“$”) should be used to specify the type of data that will be held in it. The following list signifies the different prefixes and their data type significance.
$a - Array (the following letter describes the data type taken from the rest of the data types below)
$b - Binary data
$h - File or window handle
$i - Integer
$f - Boolean
$n - Floating point number
$s - String
$v - Variant (unknown/variable type of data)
The rest of the name uses capitalized words to describe the function of the variable. Names like “$iC” are unacceptable. "$aiWeekDayNames" or "$iCounter" are much preferable.

http://www.autoitscript.com/autoit3/udfs/UDF_Standards.htm

See:

Local $bool = False
If Not $bool = True Then MsgBox(0, "Bool comparison", "OK")

And

Local $pos = MouseGetPos()
MsgBox(0, "Mouse x,y:", $pos[0] & "," & $pos[1])

Regards,

João Carlos.

Edited January 2, 2012 by jscript

[AZJIO]

guinness

Add

(?=...)
(?!...)
(?<=...)
(?<!...)
s = [fnrtvh ]
etc

Add examples

(?imsx:Text)
[[:upper:]]{2}
(?i)(Text) or ((?-i)Text)
(?is)(Text) or ((?imsx)Text)
etc

[Chimaera]

The text below could be applied in the variables of examples too!

Variable Names
The first set of characters after the dollar sign (“$”) should be used to specify the type of data that will be held in it. The following list signifies the different prefixes and their data type significance.
$a - Array (the following letter describes the data type taken from the rest of the data types below)
$b - Binary data
$h - File or window handle
$i - Integer
$f - Boolean
$n - Floating point number
$s - String
$v - Variant (unknown/variable type of data)
The rest of the name uses capitalized words to describe the function of the variable. Names like “$iC” are unacceptable. "$aiWeekDayNames" or "$iCounter" are much preferable.

This would be helpfull for the lessor mortals as im trying to learn to add these atm and i couldn't find this list

Plus could we have a little breakdown of what each type means?

I hate maths and i dont understand boolean or floating point number etc

i think binary is 0's and 1's y?

[guinness]

@jchd - I used Notepad2 to change the encoding and selected Unicode, seems I needed to select the 'Unicode with Signature' option, thanks for converting.

@jscript - It's work in progress, you'll see some examples have been tidied up e.g. DriveGet/Set functions, but these are primarily for creating UDFs and don't necessarily have to apply to the Help examples, though it does help with debugging to know what variable returns what data type.

@AZJIO - Thanks, I will have a look at those.

@Chimaera - This isn't a requirement for when coding with AutoIt, but it can help to tidy up your code and is useful for UDFs, since anyone who comes across it for the first time can see what variable is what, for example a string, boolean (True or False), array etc...and perhaps some good reading >> https://en.wikipedia.org/wiki/Floating_point

[Chimaera]

@Chimaera - This isn't a requirement for when coding with AutoIt, but it can help to tidy up your code and is useful for UDFs, since anyone who comes across it for the first time can see what variable is what, for example a string, boolean (True or False), array etc...and perhaps some good reading >> https://en.wikipedia.org/wiki/Floating_point

I know its not a requirement m8 just thought it would be usefull in plain sight to encourage good practice

Thanks for the link but my eyes glazed over by the third line Significant digits × base^exponent WTF Ill stay stoopid much easier and please don't bother to explain it.....

[guinness]

I know its not a requirement m8 just thought it would be usefull in plain sight to encourage good practice

If people are interested then they will find it as this can be easily found in the AutoIt wiki.

Also you've probably seen this already >> http://www.autoitscript.com/wiki/UDF-spec

Edited January 2, 2012 by guinness

[Chimaera]

Ok ive looking for a while m8 several months, i remembered seeing a convo about it with Melba where someone expalined all the bits but never been able to find it since

But thanks for having a look

[guinness]

See my edit above.

[Chimaera]

From that UDF page

(AutoIt has support for all OS' from windows 2000)

Haven't we dropped support for 2K now?

[guinness]

Compatible with Windows 2000 / XP / 2003 / Vista / 2008 / 7

[Mat]

@all

If there are any problems or suggestions with that page then please do PM me and I'll update it. It is still a work in progress and all of it was written by me from what the UDFs already use and what I think should be used. There are bound to be problems with it.

[BrewManNH]

From the help file for FileFindFirstFile:

?? seems equivalent to * (not described in Microsoft documentation).

That does not work in any implementation in Windows, it doesn't even work that way in Autoit3. I tried it with the example script for FileFindFirstFile, and it didn't give the same results as if I had used "*".

[GEOSoft]

there are a few things about wildcards that are questionable but I'm not sure they need changing since even MS can't keep it straight.

Example;

Windows will read "*.*" as "*". It totally ignors the "." and always has.

[czardas]

Very silly!. I'm pressuming '*>>>anything inbetween wildcards<<<*' is not supported. I'll have to run some tests on this to find out.

Edit

Manadar's next post explains a lot, although using multiple wildcards with different software still seems a hit and miss affair to me.

Edited January 2, 2012 by czardas