Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nested sorting #1702

Closed
cyberduck opened this issue Jan 25, 2008 · 2 comments
Closed

Nested sorting #1702

cyberduck opened this issue Jan 25, 2008 · 2 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 25, 2008

7d5311d created the issue

First off, thank you so much for this great product.
I use it with TextWrangler and works like a charm!

Here is what you can do to dramatically stand out from the FTP s/w makers crowd.

It's all about sorting the files.
Ok, you got the clickable colomn headings that toggles. But that's what everybody has.
What nobody has is this.
sort within sort.

here is how it goes.
you click on TYPE and it sorts. that is folders at the top.
then you click on FILENAME, than it keeps the folders at top but sorts folder names and filenames alphabetically WHILE KEEPING folders still at the top honoring the previous TYPE sort.

Currently, the moment you click on "filename" sort, folders get scattered according to their names etc, looks very untidy and its totally useless.

For those who wish to use this approach, OK, you can let them DOUBLE CLICK on the colon headings. and the end result would be currently available sorting behaviour.

What say you?
Thanks

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 26, 2008

@dkocher commented

Currently we use the expected sorting behavior as described in the interface guidelines.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 11, 2008

@dkocher commented

We do support that if the new sort comparator (e.g. size) is equal, the files are ordered depending on the previous sort comparator. But what this ticket describes is not what users would expect, I think.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants