-
-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Decide if drag&drop room lists should come back #8614
Comments
+1 to bringing it back |
(before we end up with a billion +1 comments, please use github reactions on the top comment instead) |
Is there another way to reorder rooms within the same section? I used to use drag and drop to do this. It's not clear from the description if there's another way to do this or whether it's currently impossible in the redesign. |
currently impossible; workaround is to use https://tags.t2bot.io |
Discussing this with Nad and Amandine yesterday - we're all keen for drag and drop to come back if we can guarantee that we will execute and maintain it well. If we do it, I want us to do it so that:
My personal bias is that we implement our UX such that it works stably and well without drag and drop, and then once that solid baseline is in place, consider then whether it's worth the additional investment to add a robust dnd layer on top. |
This issue seems relevant: #8723 It claims that a "labs" setting exists to re-enable room user-tags, but I can't find such a labs setting. Please bring back this feature. I used it extensively to group related rooms. Now they're all in one big "rooms" group, which is useless to me. |
(As mentioned in #8723, it's available on https://riot.im/develop only at the moment.) |
I agree with everything on the list, except the "undo" line. I think undo in a drag-n-drop situation should be fairly easy to do manually - especially if you can only drag one item at a time. I am not opposed to the undo feature, but if implementing "drag-n-drop undo" requirement is a big hurdle, I would rather see everything else implemented without this. |
I don't think any features in any software I've used fulfill that list of requirements. For example, file managers don't have finely tuned heuristics to avoid accidental drag and drop, and that's in a context where such accidents could cause data loss. We're talking about room tags here. The worst that could happen is that a user would have to drag and drop a room into a tag again. |
Perhaps one option could be to make the order lockable from the settings? I at least don't want to re-order my rooms very often, and would be fine with having to untick an option to be able to re-order them and then re-tick the option. |
I'm in favour of click and dragging between sections, such as 1:1 or rooms to favourites, etc. Like, that's just so convenient, why not have it? IMO |
I've closed/linked a bunch of issues above in favour of this one. If/when we do bring the feature back, the above issues should be considered. |
Drag & Drop stuff is always welcome! |
+1 dragging and dropping makes organizing so much more easier. |
That could work if there was a single clear question to react to. I would like to give a +1 to supporting drag and drop and a -1 to ripping that support out. I would also like to be able to drag a room between spaces because I'm sure that somehow in the past I have had success in getting People (DM rooms?) from home into spaces, but by default they always seem to get created in home, even if I used a space's People + button to start a new chat. |
Definitely it would help to sort rooms inside a space in other ways than alphabetically and drag-n-dropping them between spaces. |
Has there been any progress made for this issue since 2022? I'd love to see this feature brought back. |
Dragging between sections would likely be desirable, dragging to specify a manual sort order is unlikely desirable with Product |
Currently we don't support dragging rooms between tags on the redesign. We should either support it or rip out all the code which supports it.
The text was updated successfully, but these errors were encountered: