Report Help File Issues Here

[Mat]

I stand corrected (though by myself), there are shutdown reason codes here: http://msdn.microsoft.com/en-us/library/windows/desktop/aa376885(v=vs.85).aspx

I'll check with TranceXX that this is the case, and if it's ok I'll add those constants and document the reason code.

[JohnOne]

Thing is, it does not even mention what type it is and can lead it to fail if used incorrectly.

[Mat]

Don't use that parameter.

If you want to give a reason code then use the winapi.

[JohnOne]

Perhaps, but I believe it works correctly if the correct code(s) are added to param 2, but it is still a help file issue nonetheless.

cheers.

[Mat]

Perhaps, but I believe it works correctly if the correct code(s) are added to param 2, but it is still a help file issue nonetheless.

cheers.

Nope.

It is a helpfile issue though.

[guinness]

I will leave this with you Mat if you're contacting trancexx.

[BrewManNH]

The help file doesn't mention the fact that variable and function names are case insensitive. SomeFunc() is the same as SomefUnC() to AutoIt.

[guinness]

The help file doesn't mention the fact that variable and function names are case insensitive. SomeFunc() is the same as SomefUnC() to AutoIt.

Done.

[Richard Robertson]

The help file doesn't mention the fact that variable and function names are case insensitive. SomeFunc() is the same as SomefUnC() to AutoIt.

Really? I wonder at what point I learned that then.

[guinness]

Really? I wonder at what point I learned that then.

Messing around with code perhaps. I can't seem to locate any mention of it. Can you? Edited January 24, 2013 by guinness

[BrewManNH]

I did a search for case sensitive, insensitive and sensitive, all I found was some changelog entries that didn't deal with variables or functions.

[jchd]

I know of no mention that AutoIt language is case-insensitive.

[Richard Robertson]

I wonder if it was documented in AutoIt2 and I assumed (rightly) it carried over?

[guinness]

I wonder if it was documented in AutoIt2 and I assumed (rightly) it carried over?

Nope, couldn't find it there either.

Edit: Wow, the syntax is totally different and usage. I will stick with v3.

Edited January 25, 2013 by guinness

[AZJIO]

RegRead

Add a table

IniRead

Specify that returns a string data type

History of AutoIt and Developers (.TOC)

AutoIt and Developer History (Title)

_ArrayDisplay

$sheader

_GUICtrlComboBox_ReplaceEditSel

; Limit text in edit box

_GUICtrlComboBox_ReplaceEditSel($hCombo, "New Edit Text")

_GUICtrlComboBox_ShowDropDown

; show drop down

_GUICtrlComboBox_ShowDropDown($hCombo)

hide

_GUICtrlComboBox_AddString, etc.

; Add files

_GUICtrlComboBox_AddDir($hCombo, "", $DDL_DRIVES, False)

_GUICtrlComboBox_SetCueBanner

GUICreate("ComboBox Get Count", 400, 296)

Edited January 28, 2013 by AZJIO

[guinness]

I will look at your changes in the next couple of days, unless another MVP (most notably Mat) decides to edit in between then.

Edit: And AZJIO, try to be more specific please in the future e.g. are these in the include files, help section (.txt) or the examples?

Edited January 29, 2013 by guinness

[Mat]

I did have a look at the first point:

RegRead

Add a table

For REG_DWORD: The internal variable type is a double (as returned by VarGetType), but data is truncated to an integer when writing as REG_DWORD so the result can't be a double. "Int64, 32 bits" is just going to confuse people so I'm going to change the REG_DWORD return type to just be "A 32 bit integer". I agree that a table is a better way to display this information though.

I can't seem to see what REG_EXPAND_SZ does.

#include <Constants.au3>

RegWrite("HKCU\Test", "test1", "REG_SZ", "%PATH%")
RegWrite("HKCU\Test", "test2", "REG_EXPAND_SZ", "%PATH%")

$vVal = RegRead("HKCU\Test", "test1")
$vVal2 = RegRead("HKCU\Test", "test2")

MsgBox($MB_SYSTEMMODAL, Default, "SZ: " & @TAB & @TAB & $vVal & @CRLF & "EXPAND_SZ: " & @TAB & $vVal2)

RegDelete("HKCU\Test")

[Mat]

Guinness, while I remember, could you please make sure any new examples you write don't have side effects on the system? For instance the RegWrite example leaves keys and values in the registry, it should have some RegDelete calls at the end to tidy up (I'll fix that when I add the table).

Same goes for any File* functions. I seem to remember FileCopy copying the entire user directory somewhere else on the hard drive. That's a pretty extreme case, but there are probably others that leave mess behind.

Edited January 29, 2013 by Mat

[guinness]

Those functions you mentioned I haven't touched yet, also look at the changes I made to the File functions a couple of days ago (not FileCopy/Move yet) and you will see this is what I've been doing. Same for the Win functions where Notepad wasn't being closed.

Edited January 29, 2013 by guinness

[guinness]

If someone does have the urge to re-write the GUI examples, then this is the structure I'm looking for.

GUICreate:

#include <GUIConstantsEx.au3>
#include <WindowsConstants.au3>

Example()

Func Example()
    ; Create a GUI with various controls.
    Local $hGUI = GUICreate("Example1")
    Local $iOK = GUICtrlCreateButton("OK", 310, 370, 85, 25)

    ; Display the GUI.
    GUISetState(@SW_SHOW, $hGUI)

    While 1
        Switch GUIGetMsg()
            Case $GUI_EVENT_CLOSE, $iOK
                ExitLoop

        EndSwitch
    WEnd

    ; Delete the previous GUI and all controls.
    GUIDelete($hGUI)
EndFunc   ;==>Example

GUICtrlCreateButton:

#include <GUIConstantsEx.au3>

Example()

Func Example()
    ; Create a GUI with various controls.
    Local $hGUI = GUICreate("Example", 300, 200)

    ; Create a button control.
    Local $iNotepad = GUICtrlCreateButton("Run Notepad", 120, 170, 85, 25)
    Local $iClose = GUICtrlCreateButton("Close", 210, 170, 85, 25)

    ; Display the GUI.
    GUISetState(@SW_SHOW, $hGUI)

    Local $iPID = 0
    While 1
        Switch GUIGetMsg()
            Case $GUI_EVENT_CLOSE, $iClose
                ExitLoop

            Case $iNotepad
                ; Run Notepad with the window maximized.
                $iPID = Run("notepad.exe", "", @SW_SHOWMAXIMIZED)

        EndSwitch
    WEnd

    ; Delete the previous GUI and all controls.
    GUIDelete($hGUI)

    ; Close the Notepad process using the PID returned by Run.
    If $iPID Then ProcessClose($iPID)
EndFunc   ;==>Example

Edited January 29, 2013 by guinness