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

Delay of replacement in list after mouse move. #4888

Closed
smasharov opened this issue Jun 25, 2018 · 4 comments
Closed

Delay of replacement in list after mouse move. #4888

smasharov opened this issue Jun 25, 2018 · 4 comments

Comments

@smasharov
Copy link

Sometimes I want to select one chat in the list. I move mouse pointer to it. While clicking mouse on the needed item, item is replaced and I select wrong chat, because of replacement just a moment before click. It is more annoying if I wrongly selected channel with a hundred of unread messages, that I planned to read later, but they are all already marked as read. #775

It is happening because I got new message in the chat currently lower in the list than chat needed by me.

I think it should be delay before replacement of list during several seconds after I move mouse pointer on a list item.

@enchained
Copy link

Oh, I know that situation too well. What is you version? Cause just yesterday I "mis-clicked" on a channel and it wasn't marked as read due to the new feature/bug from the counter issue.
Also, I want to warn you - even when the counter doesn't reset on the tdesktop, it does reset for me in telegram x most of the times when I open the channel in tdesktop.

@john-preston
Copy link
Member

@enchained It is reset on the server, but tdesktop buggily shows it as unread once again. If you restart the app to reload the data it will be read already.

@stek29
Copy link
Contributor

stek29 commented Jun 27, 2018

#1504

@github-actions
Copy link

github-actions bot commented Mar 7, 2021

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 7, 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

4 participants