XYplorer Beta Club

ghost zero wrote:combining commands into one ctb is not the same as having a dedicated button. the activation method is different.

How about assigning a KS to a UDC then?

i appreciate the suggestion. but ive thought about it before and i prefer to keep consistent with the toolbar view buttons if possible. i have in mind a group of view/sort buttons visible on the toolbar that also stays pressed to indicate status.

ghost zero wrote:i appreciate the suggestion. but ive thought about it before and i prefer to keep consistent with the toolbar view buttons if possible. i have in mind a group of view/sort buttons visible on the toolbar that also stays pressed to indicate status.

That's fine. My job is to suggest a potential alternative, your job is to decide whether that alternative is suitable. Please do bear in mind that the kind of tactile feedback that you are asking for is probably CTB 2.0 at the earliest and that's not even on the roadmap

is it really that much harder to add more than 16 ctb?

ghost zero wrote:is it really that much harder to add more than 16 ctb?

That one is over to Don. I'd expect that either technical or time limitations (or both) were in the way of him implementing more. While I wouldn't mind more CTBs, I became more efficient by combining several scripts into one button.

to me, the combining scripts into one button doesn't work as well. because i would prefer the script to be run on a simple click rather than going through a right click menu. i also like to assign custom icons to the buttons. it's a shame to have such create scripting functions but then a lack of ctb to make more use of them.

ghost zero wrote:to me, the combining scripts into one button doesn't work as well. because i would prefer the script to be run on a simple click rather than going through a right click menu. i also like to assign custom icons to the buttons. it's a shame to have such create scripting functions but then a lack of ctb to make more use of them.

There will be 32 user buttons shortly. I'm currently concentrating on error 10 full power...

thanks, really looking forward to make more custom buttons!

also, can we have dedicated buttons for "sort by name" & "sort by modified date" (have ascending/descending versions for both). since you agree these 2 are the most used, it would be useful to have pressed down versions of them to always indicate the current sort mode on the toolbar (like the "views" buttons). by having the buttons pressed down, we don't have to go through a menu to check what sort mode is being used.

ghost zero wrote:thanks, really looking forward to make more custom buttons!

also, can we have dedicated buttons for "sort by name" & "sort by modified date" (have ascending/descending versions for both). since you agree these 2 are the most used, it would be useful to have pressed down versions of them to always indicate the current sort mode on the toolbar (like the "views" buttons). by having the buttons pressed down, we don't have to go through a menu to check what sort mode is being used.

It might be best to add 2 user-programmable buttons (column; asc/desc) -- preferences differ... but later...

is there a scripting command that can make the buttons look pressed from a certain criteria?

ghost zero wrote:is there a scripting command that can make the buttons look pressed from a certain criteria?

I've been thinking about this but it's difficult. The problem is that XY (lacking human intelligence) cannot know which events to watch to update the buttons states based on a script. And it is not a good idea (if at all possible) to watch every event.