[Identified] How to make a proper header in the _ArrayDisplay list view? Parameter transfer issue.

[LarsJ]

With the $hUser_Function parameter you can show two _ArrayDisplay windows side by side. How do you make a proper header in the _ArrayDisplay list view to the right? The entire header is shown in "Col 0". How do you transfer the header parameter in the proper way through the user function?

I'm running the code directly in SciTE.

#include <Array.au3>
; _ArrayDisplay( $aArray, "ArrayDisplay", "", 0, Default, $sHeader = "", Default, Default, $hUser_Function = 0 )

Global $aArray = [ [ "0/0", "0/1", "0/2", "0/3", "0/4" ], _
                   [ "1/0", "1/1", "1/2", "1/3", "1/4" ], _
                   [ "2/0", "2/1", "2/2", "2/3", "2/4" ], _
                   [ "3/0", "3/1", "3/2", "3/3", "3/4" ], _
                   [ "4/0", "4/1", "4/2", "4/3", "4/4" ], _
                   [ "5/0", "5/1", "5/2", "5/3", "5/4" ], _
                   [ "6/0", "6/1", "6/2", "6/3", "6/4" ], _
                   [ "7/0", "7/1", "7/2", "7/3", "7/4" ], _
                   [ "8/0", "8/1", "8/2", "8/3", "8/4" ], _
                   [ "9/0", "9/1", "9/2", "9/3", "9/4" ] ]

_ArrayDisplay( $aArray, "Click ""Run User Func""", "", 0, Default, "A/0|B/1|C/2|D/3|E/4", Default, Default, UserFunc )

Func UserFunc( $p1, $p2 )
  Local $hWnd = WinGetHandle( "Click ""Run User Func""" )

  Local $aPos = WinGetPos( $hWnd )
  WinMove( $hWnd, "", $aPos[0]-400, $aPos[1] )

  _ArrayDisplay( $aArray, "ArrayDisplay right window (header?)", "", 0, Default, "A/0|B/1|C/2|D/3|E/4" )

  WinClose( $hWnd )
EndFunc

I hope there is someone who can give me the answer before I get to spend the entire weekend on this annoying problem.

Regards Lars.

Edited September 11, 2015 by LarsJ
window --> list view

[KaFu]

How about this?

_ArrayDisplay( $aArray, "ArrayDisplay right window (header?)", "", 0, "", "A/0|B/1|C/2|D/3|E/4" )

[LarsJ]

It doesn't work for me in 3.3.10.

[BrewManNH]

The problem is in the _ArrayDisplay function. When you use "" or Default, the default DataSeparatorChar is reset to "?" instead of "|". When the function ends, it resets it back to "|", but because you're using _ArrayDisplay inside the user function, it jumps out of the function before it's reset back, so the separator character is set to "?" and your _ArrayDisplay doesn't separate the column headers correctly. Even when you specify the separator character, the stringsplit function inside the _ArrayDisplay function is still using "?" as the separator.

[iamtheky]

so just drop the opt in the func?  and $aArray in the func should be $p1, right?

Func UserFunc($p1, $p2)
   Opt("GUIDataSeparatorChar", "|")
  Local $hWnd = WinGetHandle( "Click ""Run User Func""" )
  Local $aPos = WinGetPos( $hWnd )
  WinMove( $hWnd, "", $aPos[0]-400, $aPos[1] )

   _ArrayDisplay($p1, "ArrayDisplay right window (header?)", "", 0, Default, "A/0|B/1|C/2|D/3|E/4" )

  WinClose( $hWnd )
EndFunc

 

Edited September 11, 2015 by boththose

[LarsJ]

KingBob, Thank you. You are completely right. A solution is to change this line in _ArrayDisplay function:

;Local $sAD_Separator = ChrW(0xFAB1)
Local $sAD_Separator = "|"

 

[jchd]

Honestly I wonder how that CJK compatibility character found its way as a delimiter.

[BrewManNH]

CJK?

Never mind, I looked it up.

I hadn't realized that it wasn't actually "?" being used, because my SciTE console window wasn't set to display non-ASCII.

Edited September 11, 2015 by KingBob

[jchd]

Ha, sorry for being cryptic. I just looked up my Unicode SQL table to check that my guess was right. This poor 0xFBA1 character has no use here, there exist a much more sensible ASCII and ANSI and Unicode codepoint well suited for that purpose: unit separator 0x1F even if its primary use was for punched card devices...

Anyway, not resetting the changed separator before invokation of the callback was indeed the culprit.

[Melba23]

jchd,

Honestly I wonder how that CJK compatibility character found its way as a delimiter

Because you suggested it! We needed to make sure that you could display whatever character was selected as the current delimiter if it occurred inside the array being displayed, so the actual delimiter needed to be set to something unlikely to be used and you proposed a "user-defined Unicode character" -the specific choice of "0xFAB1" was a personal joke that met the requirements you set.

If you now feel that "0x1F" is more suitable, I will change the UDF accordingly.

M23

Edit: It was discussed in this and subsequent posts.

Edited September 12, 2015 by Melba23

[jchd]

Sorry, memory didn't serve when previously mentionned 0xFBA1 (ARABIC LETTER RNOON FINAL FORM) instead of 0xFAB1 (CJK COMPATIBILITY IDEOGRAPH-FAB1).

Anyway, the private use area in the BMP (basic multilingual plane, the only range we can use since AutoIt use UCS-2 limited to 0x0000..0xFFFF) is 0xE000..0xF8FF.

If I indeed suggested 0xFAB1 then it must be because I was out of myself at that time, I plead guilty for that and beg all the pardon I can get, if any. (I've since stopped mayonnaise injections.)  Note that it's still pretty unlikely that anyone would be seriously affected after all.

What can be inconvenient about a control character like 0x1E (RECORD SEPARATOR) or 0x1F (UNIT SEPARATOR) is that it may not be visible if misused:

MsgBox(0, "", "abc" & Chr(0x1F) & "def" & ChrW(0xEDDA) & "ghi")

 

[JohnOne]

because my SciTE console window wasn't set to display non-ASCII.

Anyone remember how do you set it to do this?

[jchd]

I don't remember which line works, but put both in user properties:

code.page=65001
output.code.page=65001

 

[LarsJ]

Melba23, If you are going to update the code, you should reset the original separator character before the user function is called, and set it again when the user function returns. This would solve the issue in first post.

This has the advantage that when the code in the user function is being executed, it's executed in the user's original AutoIt environment. And not with a special separator character which the user is not aware of.

Lars.

Edited September 12, 2015 by LarsJ

[Melba23]

LarsJ,

I was already intending to do just that.

M23

[LarsJ]

Thank you.