XYplorer Beta Club

Hello,
I am a new (Lifetime License Professional) user of XYplorer for about 2 or 3 weeks and of course love it. I am glad I finally found it out on the internet.

One thing I have not been able to find yet is a way to get at the 'property' options that are available in the GUI when doing a Configure Custom Column. These are the options of: Caption, Type, Format, Trigger, etc...

What I would love to be able to do via scripting is toggle the 'Trigger' property back and forth between Click and Browse. (With an individual custom column identified by its Caption. The Caption here in Configure Custom Column-- not the caption when you right-click a column header in the display list and change its display name on the list-- which for me can sometimes be temporary.)

I did have multiple custom columns that were set to Trigger Click and then used right-click > Refresh Column on its column header in order to fill in the data, as well as using the click symbol icon on individual items in the list, but that became tedious mousing pretty quick when multiple custom columns were used and changing folders (rightfully) re-sets everything back to the Click position.

If this is already possible via scripting and I just haven't been able to find it yet then awesome! If not, then hopefully this is something that could be added.

Thank you!

CCs are stored in XYplorer.ini, you could change it there (via scripting) but it would require a XY restart to reflect such a change, on the fly: afaik not possible atm

highend wrote: ↑17 Jul 2023 15:04 CCs are stored in XYplorer.ini, you could change it there (via scripting) but it would require a XY restart to reflect such a change, on the fly: afaik not possible atm

Thanks for the info... that's what I thought was probably the answer. Hopefully that scripting functionality can be added in the future.

In the meantime I get by with turning all of the Custom Columns on as 'Browse' and then just having multiple named column layouts (some layouts that include those custom columns and some that don't) and just quickly move between the different named column layouts.

Thank you!

If you are interested in an alternative in the meantime that you may not have considered, you could have 2 identical columns, one with each trigger, and just toggle between each column via scripting. eg setcolumns()

jupe wrote: ↑18 Jul 2023 03:34 If you are interested in an alternative in the meantime that you may not have considered, you could have 2 identical columns, one with each trigger, and just toggle between each column via scripting. eg setcolumns()

Bingo!

Yes, that is not only a good alternative but functionally (number of necessary clicks and choices) will be just as convenient as what I originally wanted. With 64 available custom column definitions using up a few extras to double-up on existing custom columns with just a trigger change from 'Click' to 'Browse' will be a 100% workable solution. Since those are script custom columns, I will just have to remember to copy over any scripting changes between each of the pairs, but that is no big deal.

That'll work. Thank you!

I will just have to remember to copy over any scripting changes between each of the pairs

Just load script files from your custom columns instead doing the scripting inside of them. Then there is no need to replicate any changes

highend wrote: ↑18 Jul 2023 07:39

I will just have to remember to copy over any scripting changes between each of the pairs

Just load script files from your custom columns instead doing the scripting inside of them. Then there is no need to replicate any changes

Yes, thank you! I just made that switch at this suggestion.

That is so much better as the different variations ('Click' vs 'Browse') can all Load() the same script.

Is this a good practice for all of my custom column scripting? I really like the idea of storing all of the custom column definitions in a single text file (.xys) for easy editing and reference, but is there any problem with everything always being Loaded() from the disk in terms of performance/use versus the scripting being 'inside' the custom column configuration? If there is no problem with this then that is the way I will go-- luckily I do not have so many custom column definitions yet that I cannot easily switch all of them over to this practice.

Thank you

Depends a bit on if the script comes from a SSD or HDD (seek time). Windows file caching should smooth it out (with HDDs). I'm only loading external script files, regardless where but I've switched to SSD systems only > 10 years ago...