Report Help File Issues Here

[iamtheky]

Yeah thats my bad,

Function Reference

FileCreateNTFSLink

Rover just posted this updated link in the topic thread

http://elsdoerfer.name/ntfslink

Edited December 9, 2010 by iamtheky

[GEOSoft]

Thanks, fixed.

Edited December 9, 2010 by GEOSoft

[GEOSoft]

That is a neverending problem because MS keeps changing the links. They were all checked not long ago but I'll look again.

[BrewManNH]

The help file says that the @ScriptDir macro "Result does not contain a trailing backslash", but this is not true if the Script Directory happens to be the root of a drive. Shouldn't this be noted?

Fortunately, doubling a backslash in a file name doesn't affect the outcome. It should be noted in the help file, but it's not a script breaker if you forget it either.

[GEOSoft]

We can toss that one around with a developer but I see no reason to not make a very slight change.

Edit for clarification;

The proposed change would be to make an exception if @ScriptDir is the root of a drive not to add a note that Windows will ignore a double backslash.

We can't start making notes about all of Windows idiosyncrasies or we will end up confusing people with things like

to Windows; using the archaic *.* means exactly the same as *

Edited December 11, 2010 by GEOSoft

[Tlem]

Hello GEOSoft.

I have noticed something strange in some text files of the autoit-docs-v3.3.6.1-src.exe.

It seems that for some files of txtKeywords dir; in section ###Related###, some references are indicated by a url and some other have no url !!!

In first view, all the file of txtFunctions dir are with no url in reference of ###Related### section (I havn't verified all the files).

For example :

In file Static.txt of the txtKeywords dir, we can see the both case.

###Related###
<a href="Dim.htm">Local</a>, UBound, ReDim, <a href="../functions/AutoItSetOption.htm#MustDeclareVars">AutoItSetOption</a></b>

Is it a mistake, or is it normal ...

Edited December 13, 2010 by Tlem

[GEOSoft]

It's a mistake. I've corrected some already and I check them as I get to them.

[Tlem]

Ok, so which form choice?

###Related###
Local, UBound, ReDim, AutoItSetOption

or

###Related###
<a href="Dim.htm">Local</a>, <a href="UBound.htm">UBound</a>, <a href="ReDim.htm">ReDim</a>, <a href="../functions/AutoItSetOption.htm#MustDeclareVars">AutoItSetOption</a></b>

[GEOSoft]

Use the links.

[Tlem]

ARRRGHHHH !!!

By your response, you told me that 95% of the text files from txtFunctions and txtKeywords dirs in autoit-docs-v3.3.6.1-src.exe are different from the file used for AutoIt3.chm ...

But, who's compile the chm file and what files did he use?

Isn't it possible to have the same files that where used for the compilation of the chm file?

The translation of the documentation is a hard work, and those how do that, doing it for the community. So if dev team can help to give the last files, it can be a really good news.

[GEOSoft]

You will have all the corrected files for the next release.

[Tlem]

Ok, but what about the links of the related section?

Are they automaticaly added or did we must do it in the hand, file by file, function by function?

[GEOSoft]

File by File and Function by Function if you are talking about the links on the Text pages. I know there a several missing and they will get caught up. Right now we have several members working on fixing the help files and we will get to all of them but you have to remember that everyone is a volunteer including the Devs, and each one has a life of his own as well so things may not happen on your (or anybody elses) schedule. We all live with it.

[Tlem]

I have scheduling nothing, and like you said, we all have a life.

My remark is just for pointing that for compiling the last help file, somebody had to have at some moment the good files.

So it's just strange that these files are not in autoit-docs-v3.3.6.1-src.exe.

As for me, it stays some more work, that the next release will have doubtless gone out before I have finished.

Thus by taking back the end of your sentence: I would live with it.

[Mat]

Is this the right place for typos? I think think we need a wording change on "Wording changes" at the top of this thread as it's potentially ambiguous

• Returns a two-element array that containing the mouse coordinates: $array[0] = X coord (horizontal), $array[1] = Y coord (vertical)

  Either:
  • Take out the "that"
  • Change "containing" to "contains"

• The button to click: "left", "right", "middle", "main", "menu", "primary", "secondary".

  Should be the button to lift up / push down (or something along those lines). Click is definitely not what it's doing.

• Handle to control

  Handle to the control

  Control ID/Handle to the control

  Handle to * control

  These is inconsistently found across the GUI UDF's. Ideally it should be "Control ID/Handle of the * control". All the UDF's do have conditional statements to allow AutoIt controls to be used, few document it.
• _GUICtrlListView_CopyItems. Needs to get in line with the standard UDF's, it's all over the place at the moment. For $hWnd_Source see above... it would not pass the debug validation if it was a control id! The example is also way too long.

[GEOSoft]

I can take care of #1 when I get back to these tomorrow. #2 will need some discussion on the best way to handle it and as far as I know we haven't really started doing the UDF portion so I'll just make a mote of those ones until we get that far along.

[trancexx]

Ideally it should be "Control ID/Handle of the * control".

Interesting.

I was under impression that it's Control ID of the and Handle to the.

I guess you learn something new every day.

[Mat]

Dunno... Maybe handle is 'of' as well. How do you propose it's worded then?

[trancexx]

Dunno... Maybe handle is 'of' as well. How do you propose it's worded then?

Correctly.

Enough off-topic. Of is off.

[nitekram]

StringInStr lists that the 'Start' paramater is [optional] - can you provide the default?

And can you tell me if it is = 1?