-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Range selection #2070
Comments
Added a USD5 bounty to this issue: https://www.bountysource.com/issues/94807779-range-selection. This is mostly to test bounties. |
|
(from VishalNehra pr #2254) |
Just learned about this Google Photos feature (thanks for that I guess) but I have some concerns about the UX. When managing files you want to be efficient and the most beneficial use-case for range selection is in my opinion to be able to quickly select a lot of files. The range select in Google Photos is either a constant speed or it will get finicky and unpredictable if you try to add some kind of acceleration. If range selection would be implemented, I think the baseline should be the "select two and click to fill between" because this enables a much faster interaction:
Whereas the Google Photos method removes the "Quickly" part from the interaction. Having both where selecting a small amount of items is practical with the Google Photos method and a large amount using the button would be ideal. |
Is there a way to implement the select two and fill between that allows for:
|
@VishalNehra you should probably claim the bounty. |
Haha I was meaning to ask but forgot 😅 |
Can you please paste a link to the documentation that describes how a user can range-select a set of files in Amaze? I found this issue when searching to figure out how to do shift+tap multi-select of files on Amaze, but after reading the entire issue, I guess it's possible but I have no idea how. Please post a link to the range-select section of the Amaze docs for myself & other readers. |
this was implemented using #2427. please check the code for further references. |
To be clear: I'm asking for usage documentation, not implementation code. |
oh! sorry for the trouble. to range select, click on an item and drag/scroll on either direction (top/bottom) to select items in between. we do not have usage documentation as of now. |
Thanks. Is there a video of this? I don't know what I'm doing wrong. If I drag down after I tap, the page just refreshes. If I try to drag "up", then the page just scrolls. Intuitively, I would expect that I could tap-and-hold to select the first item, then scroll-to and tap-to-select the last item, and then click some |
@maltfield Please enable "drag and drop" & set it to select items from the settings. |
Thanks! That helps. But I guess it doesn't work quite like I expected. I expected it to let me just tap the first & last file and it would auto-select everything between. That would be a very optimum process to select many files. But if it were a less-ideal "drag" operation, then I'd expect it to draw a square box to let me select everything "under" the square box. Because it's not a "box select", I have to zig-zag across the screen and touch every file, which is buggy and slow. |
Exactly! That's also what ES File Explorer does. It is like Shift+Click selection that desktop computers and laptops had for decades. Drag-to-select is inferior to A-to-B range selection and just slightly faster than individual selection. |
Please create a new issue for this, shouldn't take long to implement. Will take this on priority.
|
@VishalNehra per your comment above, I created a new ticket for this UX improvement |
Honestly, drag-to-select is better than nothing. But it can only select 10 to 20 items per second. A-to-B selection like ES File Explorers' can immediately select 5000 items. |
This is already implemented, select 2 files, you'll be able to fill select between them |
Apparently this has not been suggested so far, albeit very important.
Range selection
From Wikipedia:
This was a vital hallmark of ES File Explorer (the grandfather of Android file explorers, which has sadly not aged so well), and I myself used that feature a lot.
When using Amaze for the first time, it was the first thing I noticed a lack of.
Therefore, I strongly encourage implementing that feature.
The text was updated successfully, but these errors were encountered: