Report Help File Issues Here

[BrewManNH]

It's down to the use of _DateTimeSplit, which if you see from the help file accepts these variations.

What do people think? I'm thinking of adding 'see _DateTimeSplit for variation formats' instead of duplicating the same data.

I think this is a good idea to do it this way rather than having every function with their own format list, which is just repeating the same information over and over. Just add a link to the reference, and it should suffice.

[guinness]

Is there a link to latest updated helpfile?

V3.9.9.5 Aplha/Beta(available in the beta thread) reflects most of the changes I have made in the recent months. As to why I can't upload a current version is because additions or changes to AutoIt and/or help file might not make the final release, stable or beta, simple!

Those MVPs/Members who have access to SVN should be using it and not posting the issue in this thread, unless there is a valid reason as to why you can't (temporarily) use SVN.

[guinness]

I think this is a good idea to do it this way rather than having every function with their own format list, which is just repeating the same information over and over. Just add a link to the reference, and it should suffice.

Done. I opted for adding it as a remark instead as there is already a link to the function in the 'related' section. Edited December 11, 2012 by guinness

[c.haslam]

Thank you, guinness (and others)

[czardas]

It's down to the use of _DateTimeSplit, which if you see from the help file accepts these variations.

Is it possible that this is merely a coincidence and that it does not reflect the intentions of the function's creator; or is it actually a desirable, although previously undocumented, feature?

Edited December 11, 2012 by czardas

[guinness]

Look at _DateTimeSplit, it's documented that you can enter yyyy.mm.dd or yyyy-mm-dd amongst others.

[Jos]

Is it possible that this is merely a coincidence and that it does not reflect the intentions of the function's creator; or is it actually a desirable, although previously undocumented, feature?

This was intentional behaviour. I looked at the common used delimiters in Europe and implemented them.

Believe they are also described somewhere in ISO standards but don't recall the exact details any more after 9 years.

Jos

Edited December 11, 2012 by Jos

[czardas]

This was intentional behaviour. I looked that the common used delimiters in Europe and implemented them.

Okey dokey Jos. I wanted to post the question just in case it wasn't intentional and to prevent guinness from doing unnecessary work. Thanks.

[AZJIO]

_GUICtrlHeader_GetOrderArray, _GUICtrlHeader_SetOrderArray

Corrected Example

expandcollapse popup

#include <GUIConstantsEx.au3>
#include <GuiHeader.au3>

$Debug_HDR = False ; Check ClassName being passed to functions, set to True and use a handle to another control to see it work

Global $iMemo

_Main()

Func _Main()
    Local $hGUI, $hHeader, $aOrder[5] = [4, 3, 1, 2, 0]

    ; Create GUI
    $hGUI = GUICreate("Header", 400, 300)
    $hHeader = _GUICtrlHeader_Create($hGUI)
    $iMemo = GUICtrlCreateEdit("", 2, 24, 396, 274, 0)
    GUICtrlSetFont($iMemo, 9, 400, 0, "Courier New")
    GUISetState()

    ; Add columns
    _GUICtrlHeader_AddItem($hHeader, "Column 1", 100)
    _GUICtrlHeader_AddItem($hHeader, "Column 2", 100)
    _GUICtrlHeader_AddItem($hHeader, "Column 3", 100)
    _GUICtrlHeader_AddItem($hHeader, "Column 4", 100)

    ; Set order array
    _GUICtrlHeader_SetOrderArray($hHeader, $aOrder)

    ; Show order array
    $aOrder = _GUICtrlHeader_GetOrderArray($hHeader)
    For $iI = 1 To $aOrder[0]
        MemoWrite("Index: " & $iI-1 & ", Order: " & $aOrder[$iI] & ' (' & _GUICtrlHeader_GetItemText ($hHeader, $iI-1) & ')')
    Next

    ; Loop until user exits
    Do
    Until GUIGetMsg() = $GUI_EVENT_CLOSE
EndFunc   ;==>_Main

; Write a line to the memo control
Func MemoWrite($sMessage)
    GUICtrlSetData($iMemo, $sMessage & @CRLF, 1)
EndFunc   ;==>MemoWrite

In all the examples (_GUICtrlHeader_...) you need to add support for Unicode. Otherwise, the column names are not displayed.

_GUICtrlHeader_SetUnicodeFormat ($hHeader, True)

_GUICtrlHeader_GetItemAlign, _GUICtrlHeader_SetItemAlign, _GUICtrlHeader_GetItemFormat, _GUICtrlHeader_SetItemFormat

; Reset column

; Set column

Edited December 12, 2012 by AZJIO

[JohnOne]

$l_Service [optional] I dont got a clue what this does.

[BrewManNH]

I saw that one too, got a chuckle out of it, but it made me go look it up.

The $l_Service parameter should be set to 1 for FTP connections, INTERNET_SERVICE_GOPHER (value = 2) for using it with Gopher (Pre-Vista only), or INTERNET_SERVICE_HTTP (value = 3) for HTTP/HTTPS connections.

[c.haslam]

In all the examples (_GUICtrlHeader_...) you need to add support for Unicode. Otherwise, the column names are not displayed.

This seems to me to be due to bugs in the code, rather than being a defeiciency in the Help file. This thread is for Help-file issues. Perhaps you should report the need fo Unicode support in the Bug Tracker.

[BrewManNH]

I believe azjio was referencing the examples in the help file, or at the very least making mention of the fact that you can't use Unicode characters in them without setting it to Unicode first and there's no mention in the help file regarding this.

[c.haslam]

I had thought that AutoIt is completely Unicode. Is a Header control, however it is implemented, unable to do Unicode?

If so, azjio is correct in suggesting changes to the Help file.

[Mat]

I had thought that AutoIt is completely Unicode. Is a Header control, however it is implemented, unable to do Unicode?

No, you may have to set it to use unicode first though, see _GUICtrlHeader_SetUnicodeFormat.

[AZJIO]

VarGetType

Add

Local $oObject = ObjCreate("Scripting.Dictionary")

[guinness]

VarGetType

Add

Local $oObject = ObjCreate("Scripting.Dictionary")

Done.

[c.haslam]

This quote is from the Help for Dim:

To erase an array (maybe because it is a large global array and you want to free the memory), simply assign a single value to it:

$array = 0

This will free the array and convert it back to the single value of 0.

Declaring the same variable name again will erase all array values and reset the dimensions to the new definition. Declaring a variable with a simple value in the same scope will not change the value in the variable

I'm not sure exactly what the last paragraph is saying. Perhaps the first sentence should be:

Using Dim to declare the same variable name again will erase all array values and set the dimension(s) to the new value(s).

I have found that there is another use for DIm: where a vector may have 0 or >0 elements.

• Let's say it starts with 0 elements. So I code Global $vec = 0.

• It then acquires 2 elements, so I code Dim $vec[2].

• It then goes back to 0 elements, so I code $vec = 0

• It acquires 5 elements, so I code Dim $vec[5]

Case 3 above is covered by the Help for Dim, but the other cases are not covered.

Any thoughts about how to document this?

Edited December 13, 2012 by c.haslam

[guinness]

Avoid using Dim! (Help file clearly states this.)

Dim $sVariableThatIsGlobal = 'This is a variable that has ''File Scope.'''

Example()

Func Example()
    MsgBox(4096, '', $sVariableThatIsGlobal) ; That looks alright to me.

    SomeFunc() ; Call some function.

    MsgBox(4096, '', $sVariableThatIsGlobal) ; Arghh that Global changed because I totally forgot I had a duplicate variable name in 'SomeFunc', silly me!
EndFunc   ;==>Example

Func SomeFunc()
    Dim $sVariableThatIsGlobal = '' ; I totally forgot that I declared a variable already with that same name, whoops! Well I only want this to be changed in the function and not in the variable at the top.
    ; Should be OK right?

    For $i = 1 To 10
        $sVariableThatIsGlobal &= $i
    Next
EndFunc   ;==>SomeFunc

[c.haslam]

I agree that Dim should be avoided. So in my post, replace Dim with Global.