Help File/Documentation Issues. (Discussion Only)

[FireFox]

IMO, it's perfectly clear. Never had problems to understand File* functions as far as I can recall.

[AZJIO]

Melba23

If you perform a function FileWrite several times, the data will be added to the current and cleared it only 1 time.
If to carry out the FileWrite function several times, data will be added to current, and it is cleared only 1 time.

[Melba23]

AZJIO,

But you only Open the file once - and that is where the flags come in. Whether you use file handles or filenames with FileWrite the function merely writes to the (already opened and possibly emptied in the handle case) file and will, as the Help file quite correctly states:

 

"Append a text/data to the end of a previously opened file"

The flags only apply to the initial FileOpen and in that case there is absolutely no appending of any sort when $FO_OVERWRITE is used - so any reference to such behaviour is, in my opinion, misleading in the extreme.

M23

[mLipok]

in description to Static

in syntax section now there is:

Static [Scope] $variable [ = initializer ]
Static [Scope] $aArray[subscript 1]...[subscript n] [ = initializer ]

Maybe something I do not understand, but if it should not be described as follows:

[Scope] Static $variable [ = initializer ]
[Scope] Static $aArray[subscript 1]...[subscript n] [ = initializer ]

I mean now in 3.3.9.22 HelpFile:   Why [scope] is after keyword Static ?

Edited November 6, 2013 by mlipok

[Melba23]

mlipok,

The Help file does say:

 

"The Static keyword can appear on the line before the optional scope specifier, or after. e.g. Local Static or Static Local are both acceptable"

so it does not really matter.

M23

[guinness]

I personally see no issue here either.

[iCode]

StringRegExp() - broken link

This page is only a summary for the most used pattern elements. For full in-depth discussion of regular expressions as implemented in AutoIt, refer to the complete description of PCRE patterns.

 

 

link:

http://www.autoitscript.com/autoit3/pcrepattern v8.33.html

i think it should be:

http://www.autoitscript.com/autoit3/pcrepattern.html

by the way, kudos to all who rebuilt this section of the help file

[guinness]

Fixed.

[jchd]

guinness,

I intended to append version information so that in the future, old version keep pointing to the correct reference and not the last. If that's too much to ask, do what you feel right.

[guinness]

That's fair. As for now it's temporary, but Jon will need to add this file to the correct location before I will re-revert.

[jchd]

Perfect.

[jpm]

The best way would be to include the pcrepattern.html in in the .chm.

For now the www.autoitscript.com one point to the beta one so the release .chm is wrong

I can update the .chm that will also make coherent the online doc.

[jchd]

Now that the pattern description is in better shape (shameless impression), I feel little need to flood the users with yet another lengthy inline description. The PCRE reference is now only that: a reference doc which need only be consulted in rather exceptional cases. It is now similar to the MSDN links found everywhere when a lengthy, detailled description is superfluous in the help file.

The only (little) issue with a link is that the PCRE website doesn't offer a repository for PDF doc with history, but only a somehow dated man document. If we want a one-click link we have to host the file ourselves, and then the burden of a versionned link is minimal.

We have a similar situation with the other big thing I'd like to attack: a better SQLite doc, examples with a tutorial on the wiki, for instance.

[jpm]

@jchd do I understand you don't want just to insert the pcrepattern.html page in th .chm that is solving the release/beta difference if any

[guinness]

I think it would be best to host in the chm, because hosting online is no difference as we will host the version of PCRE that corresponds to the version included with AutoIt.

[jchd]

Do so if you find it's more convenient, I'm not anal about that.

[guinness]

Neither am I really.

[AZJIO]

Tutorial - Creating to GUI Calculator - (Dialog Creation)
How it could it turns in the basic tutorial,
Link does not work

 

 

Tutorial - WinZip
At drawings to clean borders. to add border="0"

 

IniReadSection

Failure: sets the @error flag to non-zero if unable to read the section (The INI file may not exist or the section may not exist)

Add: if the section is empty

_GUIImageList_Swap

Copies description _GUIImageList_Copy, although the meaning of the function to swap icons, and not just copy

_GUIImageList_DrawEx
$iDX [optional] The width of the portion of the image to draw relative to the upper-left corner of the image.
$iDY [optional] The height of the portion of the image to draw, relative to the upper-left corner of the image.

Not the height / width of the part, and the transformation of the image

_GUIImageList_Copy

Add remark: Destination should exist.

$tagIMAGEINFO

hBitmap Handle to the bitmap that contains the images
hMask Handle to a monochrome bitmap that contains the masks for the images
Why to many? After all, one image.

[mLipok]

#2530

#2531

#2532

as the following 

Tutorial - WinZip

_GUIImageList_DrawEx

_GUIImageList_Copy

$tagIMAGEINFO

at the moment, I can not comment.

[jpm]

@AZJIO

Done except for _GUIImage_DrawEx() as it is really a width/height