Add option to disable the DM roomsublist split
I believe this will be fixed by upcoming changes around the left panel
The non-perfect workaround is to enable All settings > Sidebar > People, which puts people notifications separately on left bar.
Hey, this appears to be the last issue not being closed about combining People and Rooms. I've tried the method above, but it's only merging the people from the different Spaces in a new dedicated Space, so not the actual issue.
Could we have some news from the developers? @rufuskahler & @t3chguy? Thanks a lot for your work and maintaining this software, but we've been lacking this feature -or should I say- we've been enforced to use this feature for years, and all the other issues seem to be closed without news heh.
Could we have some news from the developers? @rufuskahler & @t3chguy?
It isn't a developer-led project, its up to the product & design teams to decide how the UX works
Hey, thanks for the clarification. You posted a comment a year ago (almost day to day) saying you thought the Panel should be reworked soon. If it’s driven by the designers, is there an open ticket about this issue? How can we push to create one otherwise?
The product team are likely tracking the epic of work internally, not sure
I honestly would like this feature too. It is so useful. I have several tens of people at work, that I am chatting with and a hand full of groups with people. It is really frustrating, to always keep on scrolling in the big list in order to see the recent message (depending of type "dm" or "group"). On my phone I recently switched to fluffychat, which feels very nice on android. On my desktop, I would like to stay on element. But not having a feature of merging these messages is really a bummer.
That seems to be like 9 years old now - pending product people (impossible to get hold of, from my experience in other issues) in some invisible separate tracker, unless I'm missing something
This is fixed in the room list in labs
This is fixed in the room list in labs
Nice. Which version?
Any version with labs enabled in its config like develop.element.io & Element Nightly.
Ok, that is better. But not in minimized mode. There are cutted smaller icons of chats (going to normal size on hover) and tags without the possibility of hide them.
I really miss some minimalistic view in Element :(
@jcz1 that seems unrelated to this issue Add option to disable the DM roomsublist split
@t3chguy Sorry but i think un-split is about active chats visibility. But you can't have visibility if 2/3 or 3/4 of some space occupy unwanted elements.
@jcz1 that is not what the creator of this issue asked for, so your assumption is likely yours and only your own.
Any version with labs enabled in its config like develop.element.io & Element Nightly.
@t3chguy , thank you very much! I'm using it on develop.element.io and that is exactly what was needed so much!
Is there any estimate when this could make it's way as 'Lab' option on the regular releases?
When it is ready. Its undergoing iterations as it progresses, so until it is done it won't be released.
When it is ready. Its undergoing iterations as it progresses, so until it is done it won't be released.
Makes sense. May I kindly ask for some estimates, please? I understand - it's been in the queue for 9 years and I'm now asking about the estimate only after two weeks, but if you could share some guidelines / something - that would be of great help!
And just in case - I'm not asking about release quality release - more about an option to enable in the lab, like I'm doing in developer web version now.
I'm not involved with that project so I have nothing to give you
more about an option to enable in the lab, like I'm doing in developer web version now.
The only thing making develop.element.io different there is its config.json has showLabs: true, you can add that to any deployment/instance to allow enabling this feature before it is de-labsed in a release.
I'm not involved with that project so I have nothing to give you
I see, apologies and thanks!
The only thing making develop.element.io different there is its config.json has
showLabs: true, you can add that to any deployment/instance to allow enabling this feature before it is de-labsed in a release.
I'm trying to find an easy way to do custom builds for a while now, but it is not easy, to say at least, especially given that they have to be build automatically and regularly.
I've found your comment on pretty much the same matter from earlier and I agree about development version.
Last two questions, if you don't mind: -1. Do you happen to know who might be the person who can share an estimate on that feature release? -2. Is there any way to switch to the development version of Desktop app? Releases seems like pushing only actual Releases; there must be some development builds as well?
I'm trying to find an easy way to do custom builds for a while now, but it is not easy, to say at least, especially given that they have to be build automatically and regularly.
Config can be specified without a custom build, by just changing the configuration file. So you can leverage any other automatic updating mechanisms, docker, apt, etc.
-1. Do you happen to know who might be the person who can share an estimate on that feature release?
@daniellekirkwood
-2. Is there any way to switch to the development version of Desktop app? Releases seems like pushing only actual Releases; there must be some development builds as well?
That would be Element Nightly, https://element.io/download
Thank you, that helps!
Config can be specified without a custom build, by just changing the configuration file.
Which seems to be:
- %APPDATA%\$NAME\config.json on Windows
- $XDG_CONFIG_HOME/$NAME/config.json or ~/.config/$NAME/config.json on Linux
- ~/Library/Application Support/$NAME/config.json on macOS
as per the doc - shall anyone wonder.
That removes the urgency. If, @daniellekirkwood , you would be able to provide any estimates when it might be released - that would be absolutely brilliant!
@t3chguy , apologies if that is obvious, I'm a bit stuck - wanted to craft a script that enables both lab and setting of interest - all without user interaction, but got an issue.
echo '{ "show_labs_settings": true }' > ~/.config/Element works just fine to show the Labs,
but
"features": { "feature_new_room_list": true }
doesn't - am I right in understanding, that it is by design and I can't switch on / off specific settings that way?
Thanks in advance!
We use config to enable labs flags all the time, e.g. https://app.element.io/config.json so not sure what issue you're hitting.
We use config to enable labs flags all the time, e.g. https://app.element.io/config.json so not sure what issue you're hitting.
I've enabled New rooms feature in GUI, then tried to disable it via the config.json:
{
"show_labs_settings": true,
"features": {
"feature_new_room_list": false,
"feature_video_rooms": true,
"feature_group_calls": true
}
}
But the feature remains switch-on.
Looks like that one labs flag prefers device settings over config as supportedLevelsAreOrdered is not specified as true.
@MidhunSureshR as the person who added the labs flag, do you know the reason for this?
It seems that this is now the default since element 1.112. I'm sad because I liked mine separated
Fixed by new room list