Report Help File Issues Here

[GEOSoft]

Then I won't be worried about looking at the ones for AutoIt since you are on top of things today.

Thanks

[GEOSoft]

  On 8/7/2011 at 2:10 PM, 'Chimaera said:

Hope im allowed to suggest one

Anyone is allowed to suggest changes.

  On 8/7/2011 at 2:10 PM, 'Chimaera said:

_DateDiff

Can the remarks section be amended to clearly state that this will not work unless the date is in the correct format for autoit.

Wasted a load of time trying to work out what was wrong and i eventually twigged it was the format

I know it says this

$sEndDate Input End date in the format "YYYY/MM/DD[ HH:MM:SS]"

but i never noticed the format bit till much later

It wouldn't matter if we put that in 30 point bold, people will still skip past it and try to use the function improperly. There is only so much that can be done to draw peoples attention to the Remarks

  On 8/7/2011 at 2:10 PM, 'Chimaera said:

Edit

And maybe an example of how to reverse dates, i used this

StringRegExpReplace($file_to_change, "\A(\d*)/(\d*)/(\d*)","$3/$2/$1")

I'm not sure that something like that is appropriate for each function where it could be utilized. The longer a page is - the less chance there is of people actually reading through it.

That being said; I've actually been avoiding doing much with the help files for the UDF section. That's because there may be some upcoming changes to those UDFs anyway and whoever does them will probably have to change the docs anyway so they can be looked at when that happens.

[Chimaera]

Ok m8 well thanks for answering, On that one there is nothing in the remarks so nothing lost really.

I have said before in chat sometimes the level of the examples is a bit to high brow but its because the person writing it is viewing it from the higher perspective.

Im still waiting for an example to come up on the forum for arrays where i go Aaaaah now i get it..

I live in hope, Melba32 has tried a couple of times to help/confuse me with them

One day it will happen ...

[Melba23]

Chimaera,

  Quote

Melba32 has tried a couple of times to help/confuse me

More the former than the latter I trust.

Have you tried reading the Arrays tutorial in the Wiki?

There are quite a few tutorials on other more obscure bits of AutoIt in there as well.

M23

[water]

The online version of the help file has an invalid link in function MsgBox.

When you try to click on

"If "title" is equal to Default keyword @Scriptname is used"

in the remarks section you will get "Not found" because the URL "http://www.autoitscript.com/autoit3/docs/functions/..\keywords\Default.htm" is invalid

[GEOSoft]

That's already been corrected in the docs so I would assume it will be updated online after the next release.

[monoscout999]

About GuiGetMsg()

As @ProgAndy suggest from here

  Quote

All GUI-events are stored in a queue. GUIGetMsg reads and removes the least recent event.

[GEOSoft]

I followed that thread and made a note of it. Is it a bug? No. You were also shown the correct way to do it.

Can the help file contain every last detail about every last issue a user may come across? No.

I'll be leaving it alone unless a Dev hinks it should be changed.

[water]

Yes, but ...

Sometimes I would like the help file to contain not only what a function does but a little bit of insight how it's being done. Internals don't have to be explained to the last detail but a bit of description how things are done helps users to understand why a function behaves like it does.

But it's up to the Devs how much time/effort they want to put into the help file.

Just my 0.02€

[Valik]

Implementation details are irrelevant. If you find that implementation details are important then you're probably trying to rely on some behavior you shouldn't or the function you are using is poorly written.

[guinness]

The example for 'GUICtrlCreateMenuItem' is declaring a Global variable within a function and not at the top of the script.

Edited August 20, 2011 by guinness

[GEOSoft]

Thanks guinness.

As a matter of fact both of those globals are declared right above as Locals.

So the lines

Global $defaultstatus = "Ready"
Global $status

in the example au3 file

Should be changed to

$defaultstatus = "Ready"

Removing "Global $status" entirely and removing the Global scope from the other.

Edited August 20, 2011 by GEOSoft

[guinness]

You're right

Another one I found is shouldn't $WM_MOVING = 0x0216 be in WindowsConstants.au3?

[Werty]

Helpfile and online help

/History of Autoit and Developers/

  Quote

VALIK

A long time ago I found a Diablo II bot. For whatever reason (Probably to fix something), I learned it was written in AutoIt.....

Cool back then, but not so cool now that gamebot discussion isnt allowed anymore, maybe rewrite the sentence.

[Valik]

Why? History does not change simply because our perspective on the details do.

[Werty]

  On 8/23/2011 at 8:08 PM, 'Valik said:

Why? History does not change simply because our perspective on the details do.

Right, but the confussion it may raise to new members/users.

Also like the title in the forums "Game Automation and bots", should be "No game automation and bots" or simply "game bots discussion not allowed". (seems to have been changed, or i look the wrong place )

(fast reply btw )

Edited August 23, 2011 by Werty

[Valik]

  On 8/23/2011 at 8:10 PM, 'Werty said:

Right, but the confussion it may raise to new members/users.

If new members can't be bothered to read the forum rules I doubt very seriously they are going to read the little blurb for each of the developers in the help file.

  Quote

Also like the title in the forums "Game Automation and bots", should be "No game automation and bots" or simply "game bots discussion not allowed". (seems to have been changed, or i look the wrong place )

(fast reply btw )

That announcement has been hidden since the Forum Rules announcement went live.

[guinness]

A really minor problem & I mean 'really minor,' in AdlibRegister it states

;... execution must be non blocking, avoid ...Wait(), MsgBox(), InputBox() functions, but shouldn't it be WinWait*() or something to that effect. It was an issue that was brought up here

[Valik]

ProcessWait(), ProcessWaitClose(), RunWait(), ShellExecuteWait(), et all.

Edit: Actually now that I re-read your post... what functions actually do block Adlib callbacks because I don't know. I thought it fired during some of them.

Edited September 2, 2011 by Valik

[guinness]

Hang on ... True, now I re-read that comment too surely it would execute all those functions, well I presume it would but you know what they say about presumption!