Report Help File Issues Here

[wraithdu]

I would think anything requiring user interaction (at least) would be a blocking function, ie MsgBox(), InputBox(), I think there's a color picker dialog in there somewhere. Anything that has it's own internal message loop perhaps?

Edited September 2, 2011 by wraithdu

[RichardL]

"FileFindFirstFile

...

You can use only one wildcard in the filename part or in the extension part i.e. a*.b?.

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

I'm using XP-SP3 and things are better than they used to be, recently I've been using

No-*~*~????????_????????????????.uhh

which finds the right files, and not others that have extra chars after the 2nd ~. If I remove any of the ? It doesn't find anything.

"Directory name are return according to the wildcards if any."

- what does that mean?

- name/names?

- return is a handle, it doesn't return names?

- should it be in help for FindNextFile? and is saying that as well as files it returns any directory names that meet the spec?

Richard.

[MvGulik]

@MSEC: Note about 'it not being accurate(resolution) down to the millisecond' ?

-

-

[Valik]

@MSEC: Note about 'it not being accurate(resolution) down to the millisecond' ?

-

-

To determine the system minimum and maximum resolution use timeGetDevCaps(). To change the resolution use timeBeginPeriod(). The system uses the smallest requested (and supported) time from any application. It's theoretically possible your system isn't using the minimum supported time. Mine does and my minimum is 1 millisecond. Jon and I have already had a brief discussion about ensuring AutoIt uses the minimum supported time for reasons of or own.

I guess I can add a brief note along the lines "The update frequency of this value depends on the timer resolution of the hardware and may not update every millisecond."

[rover]

The entry for GuiSetState lacks some of the macros listed for _WinAPI_ShowWindow

@SW_SHOWDEFAULT - Sets the show state based on the SW_ flag specified in the STARTUPINFO structure

@SW_SHOWMAXIMIZED - Activates the window and displays it as a maximized window

@SW_SHOWMINIMIZED - Activates the window and displays it as a minimized window

@SW_SHOWMINNOACTIVE - Displays the window as a minimized window

@SW_SHOWNA - Displays the window in its current state

@SW_SHOWNOACTIVATE - Displays a window in its most recent size and position

@SW_SHOWNORMAL - Activates and displays a window

Edited September 19, 2011 by rover

[Melba23]

Hi,

Following on from Trac #1707, the UDF code has been changed in the Beta, but not the associated change to the Help file. _SoundPlay should have the following as a Remark:

In Vista and above, "\Windows\Media\..." files containing spaces must be opened with _SoundOpen before using this command with the returned Sound ID array.
;

The Trac ticket explains why this is the case.

M23

Edit: Needed to fix tags...yet again.

Edited September 20, 2011 by Melba23

[JohnOne]

Example for (Experimental) keyword Static errors out.

Static.au3 (37) : ==> Cannot make existing variables static.:

Static $Values[$State + 1]

Static ^ ERROR

->17:53:37 AutoIT3.exe ended.rc:1

I know it says dont report bugs, and I'm not, Static works for my tests, just the helpfile example does not.

[MvGulik]

Example is fine ... problem is ... missing 'knows issues' in Static doc.

(if there is no active development on it at the moment, dropping known issues in manual seems logical to me.)

[Valik]

It is not fine. Redim should work with Static variables. That means: 1) The example is wrong; 2) Redim needs updated to support Static variables.

[MvGulik]

0) Static help is wrongly suggesting Static instead of Redim should be used for resizing Static arrays.

"If you want to resize an array, always use Static to do so, not Redim."

Edited September 21, 2011 by iEvKI3gv9Wrkd41u

[Valik]

It is not wrongly suggesting that. That was David's initial intent but I do not like that approach as I find it counter-intuitive. Since David isn't here to fix the code and it will likely fall to me I'm exercising my prerogative as the person doing the work to change it to suit how I feel it best should work.

Either way it should be resolved at some point.

[MvGulik]

Its not? ... that's odd ...

Anyway. Until that point is revisited by someone. Updating Doc with the current Static behavior/limitations seems not a bad thing.

Edited September 21, 2011 by iEvKI3gv9Wrkd41u

[Valik]

I don't think you understand what that big warning is actually saying.

[BrewManNH]

Documentation for GUISetOnEvent/GUICtrlSetOnEvent/AdlibRegister should make mention of the fact that the function registered can't have any parameters. For example the called function Func _SomeFunction($Test) causes an error if you use the variable $Test in the function saying the variable $Test is an undeclared variable.

[MvGulik]

I don't think you understand what that big warning is actually saying.

I think I do. That don't mean that I(user) read it the way you(dev) like me to.

As User I think the manual. If it already contains information about a given feature(experimental or not). And there has not been any active development/changes on that given feature for some time. There is no reason for the documentation/manual not to be updated with known(undocumented) behaviors and limitations.

(I fail to see why Dev's though's about how a feature 'should' work are relevant in this 'documentation' matter. ... other than that Users opinions/views are irrelevant to some Dev's of course.)

That's it from me on this case.

[Mat]

Documentation for GUISetOnEvent/GUICtrlSetOnEvent/AdlibRegister should make mention of the fact that the function registered can't have any parameters. For example the called function Func _SomeFunction($Test) causes an error if you use the variable $Test in the function saying the variable $Test is an undeclared variable.

That in many cases that's useful in that you can have a 'default' value for $test y using IsDeclared. You are right that it should be mentioned but your wording is wrong. 'Parameter in the function won't be declared' is probably a better way of putting it.

Whether it's good programming to be doing that, and whether that was the intention is another story altogether.

[BrewManNH]

The problem is, you can't declare it inside the function either because that causes an error saying it's already been declared or something along those lines.

[Mat]

Maybe not explicitly... But I'm sure this has worked in the past:

If Not IsDeclared("test") Then $test = Default

Obfuscator won't like it, but it's easy when you want to save on functions wrapping more functions.

[BrewManNH]

I'll have to remember that one.

[Valik]

I think I do. That don't mean that I(user) read it the way you(dev) like me to.

As User I think the manual. If it already contains information about a given feature(experimental or not). And there has not been any active development/changes on that given feature for some time. There is no reason for the documentation/manual not to be updated with known(undocumented) behaviors and limitations.

(I fail to see why Dev's though's about how a feature 'should' work are relevant in this 'documentation' matter. ... other than that Users opinions/views are irrelevant to some Dev's of course.)

That's it from me on this case.

So you want me to stop what I'm doing and update documentation for a feature clearly labeled "experimental" so that the documentation matches the feature's behavior even though the feature is not finalized and furthermore the feature will see changes to the behavior? Please don't look at the ObjCreateInterface() documentation, then, because you just might have an aneurism at how incomplete and virtually useless it is at the moment.

On second thought please go look so maybe I won't have to deal with your retardo-logic anymore.