-
Notifications
You must be signed in to change notification settings - Fork 168
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
Chat history in a list #2310
base: master
Are you sure you want to change the base?
Chat history in a list #2310
Conversation
Thanks! I love this! I was tired of read only edit boxes that screenreader would act stupidly with it. I'm going to try it now, if it's not the case, please also do it for private messages history as wel. Thanks! |
Already done, TextMessage use the same widget as MainWindow
|
it looks like some messages are being sent as difrent peaces or something, but sometimes screenreader says list item. Look at below lines, i'll paced the items of my history list so you can understand, i'm pressing down arrow and my screenreader is nvda |
actually so many of my friends and anyone was complaning about the history system, but by moving it to list all those problems has been greately resolved |
This change does not work well for people who use a mouse since you cannot select text and use Copy/Paste. |
you can coppy the message by the context menu option, then paste it in the edit box, and then select part of it and remove it or stuf |
and read only edit text does not work wel for us with keyboard and screenreader. So, may be add an option in display tab and when checked, we use list instead of read only edit text. Just an opinion |
I also use a screen reader and I don't see how the list is better than the read-only text box. in the read-only text box, you can select a specific part of the text without having to select the whole line, and cut it out in a notepad, for example. |
in list all item is being announced all at once, but in read only text box when you receave an event that is long or has 2 lines and stuf, you have to press down arrow to read the half of that event so it's seperated, but in list, when you receave one event, focusing on that event reads all of it, from start to end, and it doesn't need you to press down arrow because just in case it's split up in to 2 lines, also, some people report that when pressing up or down arrow to view all of their history items, some events are missing for them, but with list that problem no longer exist |
I've never had the problem of the history entry disappearing when it was
in read-only mode.
but anyway, I don't think it's worth debating the subject any further.
|
yes, if some people really wants the read only edit box, an option in the display tab or another solootion by @CoBC would fix that, so |
We can't select a piece of text with keyboard as well.
So, I suggest the following: add the ability to show message in a
dialog, with potential more info, E.G. the dialog can display timestamp,
which can be useful for users who decided to don't display this info in
the history but want to see timestamp of a specific message. In this
dialog message will be shown in a edit field so we can select text and copy.
I also have the idea to allow deleting one item of the list, for users
who don't want to clear all history but just remove unwanted messages.
What do you think?
|
Yes, we also have a serious problem with navigating in the readonly edit
field with NVDA for example, some characters are repeated more and more,
other characters are skiped, multilines messages are read very strangely
with blank lines ignored. Accessibility of list is really better
compared to readonly edit field.
The real problem is if mouse interactions are broken, but I made a
suggest for it, we'll see
|
yes, exactly, those are the problems i forgot to mention. So, I strongly want the list for the history as a teamtalk user instead of read only edit box. |
@peter1384 I think everyone understands your point. |
I vote against this change. If someone wants this, this should be as an option disabled by default. |
Let me know if I should implement this as an option, but it will be a
bit complicate to do
|
@CoBC I don't really want to loos this feature. So, if it's realy the case, i'd want it as an option then, and i'm happy about the faqt that you understand the problems of the read only edit boxes |
I don't really understand how we can't have problem with this readonly
editbox, multilines fields are really problematic with Qt, especially
when a lof of blank lines are present.
So, I also want to keep this feature, but I'm not the only one to decide :)
|
And, my last thought on this topic, majority of chat apps (at least on Windows) use this type of list for message, E.G. WhatsApp, Messenger, Phone Link (for messages from Android or iOS), and probably some other. |
github desktop is using list for the history as wel, and yes as you said, I don't know how they don't have any problem with readonly editbox. everyone around me are complaning about it that it has problems |
One more advantage for the list I forgot yesterday, imagine you're receiving a very long message with an URL in the middle of this message, currently you have to read all the message with arrow keys for keyboard user to be able to press enter on the link and open it, with the list, you just have to press enter on the message and the link will open, and if multiple links are present, a menu will ask you what link you want to open. |
List is a lot better especially for NVDA users |
Hi. In regard to not being able to select messages with the mouse, I would have expected the mouse selection to work like multi-selection of files in explorer does, e.g. holding right mouse button and dragging it down the messages list, or something similar to that. Also, holding control and left single clicking each message to be selected, then right click one of them and copy. |
I also hate read only edit box for the history, and because of that i never used history for reading my messages, I always used my nvda speech history to read my messages, but with list i will use my teamtalk history from now on always. So, i also really want the list |
@CoBC can you please add an action to context menu to only delete the current item, sometimes I don't wish to clear my hole list, I just wish to delete some unwanted items from my list and keep the others that I need. So, This context menu action is needed, So please add it. Thanks. |
I'll don't make anymore commit in this PR for now until I'm sure the PR
idea is accept.
|
Can you Please also merge the master branch to this branch, because I want to use it with laytist heehee |
oh, ok then. Sad |
I opened a poll |
Current results of poll (#2313) are in favor of the list, I also received 2 positive comments for this list from users who aren't on GitHub.
|
if this will be implemented, i vote for it to be an option. |
@beqabeqa473 somethings cannot be option because they will be implemented depending on it's better for all users. For example, I didn't liked the new q table, but I didn't request it to be option because it was depended on what moste users want and like. So, you are not the only person to say what to happen, because so many people are using teamtalk and all of those people cannot be ignoared just because of what you want. So please, don't complane and get used to whatever that is. Thanks. |
@peter1384
You're always requesting something and something and something else
again, with some reasons like "we need it so please add it", so please,
be respectful with other users and contributors, if Beqa prefer this to
be an option, even if it's very difficult to implement it as an option,
it's his choice, we have to hear and understand all users. Please be
careful when you comment.
|
@CoBC yes i agree with you, I just ment that we should do what users want. so, sorry for the miss understanding |
A lot of apps use list instead of readonly edit field to display chat history now, so I thought it's time to do the same in TT
It seams to works as expected with keyboard and screenreader.
Really not sure of the behaviour visually and with a mouse
I hope it's not completely broken