Page 2 of 2
Re: Get TreeGadget full path suggestion
Posted: Sun Jun 18, 2023 10:01 pm
by Little John
Perhaps for instance #LF$ is a good choice as separator, since this character is rather unlikely to appear in an item of the TreeGadget().
Re: Get TreeGadget full path suggestion
Posted: Sun Jun 18, 2023 10:09 pm
by BarryG
Fred wrote: Sun Jun 18, 2023 7:12 pmWhich separator should be used in the sting ?
BarryG wrote: Sun Jun 18, 2023 1:55 ama new command could use #LF$ to be consistent with other commands
So it's similar to the separate fields of a ListIconGadget(). Then the user can do "ReplaceString(string$,#LF$,custom$)" if they like.
Re: Get TreeGadget full path suggestion
Posted: Sun Jun 18, 2023 11:34 pm
by idle
It would be good to have a custom separator.
Re: Get TreeGadget full path suggestion
Posted: Wed Jan 17, 2024 3:22 pm
by Axolotl
Why not implement the well known procedures together with a new constant like
Code: Select all
; NEW
; #PB_Tree_Separator .. #LS (10) (because Value is Int )
;
; GetGadgetAttribute(Gadget, Attribute)
; SetGadgetAttribute(Gadget, Attribute, Value)
; possible usage
SetGadgetAttribute(#GADGET_Tree, #PB_Tree_Separator, #LS) ; or '|' or $205E ...
Re: Get TreeGadget full path suggestion
Posted: Wed Jan 17, 2024 4:23 pm
by AZJIO
#PS$ #LS
#PS$ if #PB_Tree_Separator is present
AutoIt3 has global options without being tied to a gadget. For example Opt(#PB_Tree_Separator, #PS)