Page 1 of 1

Custom Field Seperator for inputselect(3:=1024)

Posted: 23 Nov 2025 23:35
by WirlyWirly
While working on a script, I ran into an issue when trying to create a menu with inputselect(3:=1024) and also using a regex pipe in the data field.

Something like this will break the menu, since I don't have the option to change the | separator used by inputselect(3:=1024)...

Code: Select all

::$command = inputselect('FastFinds', 'Music files|goto "?>(flac|opus|mp3)$"|:qson', ':::', 1 + 1024); load("$command", 2:='s')
Regex pipes are quite handy, so any chance we can get the ability to change the default separator away from |?

Re: Custom Field Seperator for inputselect(3:=1024)

Posted: 25 Nov 2025 16:52
by admin
Next beta you can do:

Code: Select all

::$command = inputselect('FastFinds', 'Music files#goto "?>(flac|opus|mp3)$"#:qson', ':::', 1 + 1024, 11:=#);

Re: Custom Field Seperator for inputselect(3:=1024)

Posted: 25 Nov 2025 19:19
by WirlyWirly
Updated and it's working great, thanks a bunch :biggrin:

While we're on the subject of inputselect(), I found what I believe to be a bug; Setting inputselect(3:=32) and then hitting the {Enter} key over the Cancel button will return the first selected item instead of terminating the script. {Left-clicking}the Cancel button instead of pressing {Enter} will terminate the script as expected.

You can see it here; run the script, {Tab} over to the Cancel button then hit {Enter}...

Code: Select all

::$name= inputselect('Names', 'Wirly|Don|highend', 3:=32); msg "Hey $name!";

Re: Custom Field Seperator for inputselect(3:=1024)

Posted: 26 Nov 2025 14:41
by admin
Confirmed for 64-bit. That's a tB bug. They are working on it.