Report Help File Issues Here

[AZJIO]

The first example of a simple, more difficult to second, then third is even more difficult. I'm not losing my simplicity, but for those who can understand more gets what he wants. Initially, my code was the same as in "AutoIt help" because I could not imagine a different option. I just kept repeating the movement. For example, all of my GUI have design "Select ... Case ... EndSelect", then I rewrote all scripts in the "Switch ... Case ... EndSwitch". Further, I have always created variables to get a result that is used in the condition. And again, I rework the scripts without extra variables.

Ru (my examples)

If...Then

If...ElseIf...Else...EndIf

Switch...Case...EndSwitch

MsgBox

Examples should demonstrate functionality and not confuse the user. I have to say that MsgBox would confuse me and raise questions in the forum.

For me, it opened up tremendous opportunities, and I did not know that MsgBox returns a number. Before, I did not understand why these tables on page MsgBox. I basically took the examples. If they have not opened the possibility, I just can not use them.

Show me an example where MsgBox uses the number? I found only one - "TrayItemDelete".

Edited August 18, 2012 by AZJIO

[czardas]

Looks good AZJIO.

Edited August 18, 2012 by czardas

[Mat]

Whatever the case it definitely shouldn't be in the helpfile if it uses magic numbers. We've had this discussion before.

[czardas]

What magic numbers? AZJIO is right in a way. If I want to know how to use Msgbox return values, I'm obviously going to look at TrayItemDelete.

[Valik]

What magic numbers? AZJIO is right in a way. If I want to know how to use Msgbox return values, I'm obviously going to look at TrayItemDelete.

Off the top of your head, quick, tell us what flags 4 and 32 do to a MsgBox().

[czardas]

Ouch, off the top of my head I can't remember. (shows how much I rely on the help file ) Why?

Now I have checked.

Edit

Actually there is enough information about Msgbox return values.

Edited August 19, 2012 by czardas

[guinness]

Hi,

The Help file example for StringStripCR is not very helpful as the final result does not really show what has happened. Something like this might be better:

Local $sString = "I am" & Chr(13) & " a string"
MsgBox(4096, "Original string", $sString)
$sStripped_String = StringStripCR($sString)
MsgBox(4096, "String stripped of CR characters", $sStripped_String)

M23

Done. Thanks.

[AZJIO]

Tried to make Link to functions in examples.

default.css

a.le:link {text-decoration:none;}
a.le:visited{text-decoration:none;}
a.le:active {text-decoration:none;}
a.le:hover {text-decoration:none;}

Replacement in html-files

$test=StringRegExpReplace($test, '<span class="S4">([wd]+?)</span>', '<a class="le" href="1.htm"><span class="S4">1</span></a>')

<span class="S4">Abs</span>
<a class="le" href="Abs.htm"><span class="S4">Abs</span></a>

Processing of all examples

AutoIt3(En).7z - ready example

Edited August 24, 2012 by AZJIO

[JohnOne]

I'm sorry if this has been addressed, but Number() func remarks might be a little confusing.

At least it would be to me.

Default behavior results in auto-sized integer. If input value after conversion is within the range of 32bit integer the result is 32bit integer. If not the result is 64bit integer. Both signed.

$sDouble = "1z.234s"

$_Number = Number($sDouble)

MsgBox(0,$_Number,VarGetType($_Number))

The above code tells us that $_Number is a double, not an int.

From the remarks I would expect the $_Number to be demoted to an int.

[Valik]

Actually, this is probably a bug with AutoIt. If I had to guess without looking, the code likely scans for a decimal separator - which it finds - then performs the conversion. The problem in this case is the output ends up being an integer since invalid numeric characters are found before the decimal separator. I'm not sure it's worth fixing, though.

[JohnOne]

Probably not, it is quite trivial a gripe.

I would suggest a remarks change

"Default behavior results in an auto evaluated number."

or something along those lines.

[guinness]

Tried to make Link to functions in examples.

It's an idea, but given the current situation of how the help file is built, your implementation won't work. I'm also not very keen on messing about with the build scripts.

[guinness]

GUIStyles.htm - Jump menu

Done.

[Valik]

I'm also not very keen on messing about with the build scripts.

Was it the threat of death on anybody who touches them besides me? Yeah, probably that.

[guinness]

Was it the threat of death on anybody who touches them besides me? Yeah, probably that.

It did have a part to play in my decision, yes.

[AZJIO]

VarGetType

Local $tStruct = DllStructCreate('wchar[256]')
...
    "$tStruct = " & @TAB & VarGetType($tStruct) & @CRLF & _

Edited September 4, 2012 by AZJIO

[guinness]

VarGetType

Local $tStruct = DllStructCreate('wchar[256]')
...
"$tStruct = " & @TAB & VarGetType($tStruct) & @CRLF & _

Done.

[AZJIO]

Conv_Link.7z

1. extract the archive to a folder.

2. copy AutoIt3.chm and UDFs3.chm to a folder

3. run Conv_AutoIt3.au3

4. a minute later files will be recompiled

[BrewManNH]

Since I started using AutoIt, I always thought the help file example for using StdOutRead and StdErrRead was the only way to read the StdOut and StdErr streams of a program being executed. I ran across an example from another user that showed that these streams do not need to be read in a loop while the program is running, but that they can be read even after the program has closed. I've modified the example script shown in the help file to show what I'm talking about.

; This is the example script from the help file slightly modified to use ConsoleWrite instead of a MsgBox
#include <Constants.au3>
Local $foo = Run(@ComSpec & " /c dir foo.bar", @SystemDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD)
Local $line
While 1
     $line = StdoutRead($foo)
     If @error Then ExitLoop
     ConsoleWrite("STDOUT read: " &  $line & @CRLF)
WEnd
While 1
     $line = StderrRead($foo)
     If @error Then ExitLoop
     ConsoleWrite("STDERR read: " & $line & @CRLF)
WEnd
MsgBox(0, "Debug", "Exiting...")
; This is the same example of reading StdOut and StdErr but without using a loop.
; this example shows no blank lines in the output text.
Local $foo = Run(@ComSpec & " /c dir foo.bar", @SystemDir, @SW_HIDE, $STDERR_CHILD + $STDOUT_CHILD)
While ProcessExists($foo)
     Sleep(10)
WEnd
$line = StdoutRead($foo)
ConsoleWrite("STDOUT read: " &  $line & @CRLF)
$line = StderrRead($foo)
ConsoleWrite("STDERR read: " & $line & @CRLF)

The second example shows that these streams are still able to be read even after the Run command program has exited, in fact the way it's written, they're not read until it has exited. You'll also notice that the output from the second example doesn't have the numerous blank lines that the first example shows. While this method may not be the officially approved way of reading the streams, and won't work for any script that needs to read these in real time, it should be mentioned that it's possible to do it this way in the help file, because I never knew that you COULD read them this way.

[AdmiralAlkex]

You could use ProcessWaitClose() instead of that ProcessExist() loop.