You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Once correo is connected to a MQTT-broker which receives a lot of messages at a time, the table of messages is not really usable. If you select a message, the new messages are all rendered above and your selection is no longer visible. So you have to be fast to get the detail message.
Also it is not possible to see which messages are new since there is no timestamp or something like this in the table entries.
Describe the solution you'd like
If a user selects a message and new messages arrive: the selected message is still selected and the selection is visible to the user and does not scroll all the way down.
If a message arrive: there should be a date (message received) for each message above the topic
Okay it make sense to stop the auto scrolling as soon as a message is selected.
I see some further challenges regarding this:
What if you are searching a message and want to scroll, but not select anything yet?
If auto scrolling is stopped, when to reactivate it?
I would propose a toggle icon, that behaves like this:
On per default
Automatic off if a message is selected
Automatic off if user scrolls
Automatic on if you scroll to top
User can click of course to disable/enable auto scrolling
Timestamps in the message list is already mentioned here: #66
Currently the date can be shown via right click (does not solve the current problem of course).
Is your feature request related to a problem? Please describe.
Once correo is connected to a MQTT-broker which receives a lot of messages at a time, the table of messages is not really usable. If you select a message, the new messages are all rendered above and your selection is no longer visible. So you have to be fast to get the detail message.
Also it is not possible to see which messages are new since there is no timestamp or something like this in the table entries.
Describe the solution you'd like
Additional context
I also did a sample video: https://user-images.githubusercontent.com/584963/158768182-22ba5d4a-1bea-4cba-a85a-00977a552b11.mp4
The text was updated successfully, but these errors were encountered: