XnView Software

Batch Convert: sort commands by name

klumy wrote:Batch Convert: sort commands by name

Really? Resize/Crop/Canvas are often used....

—> Pierre

Hello !

• I support the klumy's request ! This list is a pretty mess.

Really? Resize/Crop/Canvas are often used. …

• Make three buttons for them, plus a customizable “wildcard” one !

KR
Claude
Clo

xnview wrote:

klumy wrote:Batch Convert: sort commands by name

Really? Resize/Crop/Canvas are often used....

Yes, they're used frequently. I often search them down in the list and finally find them on top where they don't belong to.

It might make sense to do this like Word, Writer etc do with fonts: On top a list of last/frequently used, a horizontal line, then the complete list. Showing some items twice is less bad than not finding them

Clo's idea with a customizable wildacrd (user defined preset) is an additional approach, as long as it's not only one preset (I do around 3-4 different conversions). Distinct buttons for those tree frequently used ones are IMHO not nice as I cannot re-define / remove them - better make the custimzable ones preset with those 3 functions when shipping XnView. Then the suer can keep them or drop them.
/georg

klumy wrote:sort commands by name

I like this organisation (from 'Effects'), could it make sense in Batch Convert too?

Clo wrote:Make three buttons for them, plus a customizable “wildcard” one!

I still think that Favorite buttons is a not a good idea.

—> Olivier_G

Hello!

I still think that Favorite buttons is a not a good idea.

I've betted 1 € with myself that you'll say this !

R
Claude
Clo

Olivier_G wrote:

klumy wrote:sort commands by name

I like this organisation (from 'Effects'), could it make sense in Batch Convert too?

Clo wrote:Make three buttons for them, plus a customizable “wildcard” one!

I still think that Favorite buttons is a not a good idea.

So a tree or list with most used first??

xnview wrote:So a tree or list with most used first??

To me, they seem as equally good and both better than the current state. So whatever is easier to implement

I like the tree idea

The tree is the way to go. This would make a big difference and improve handling of transformations a lot.