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

Conversation list: Time & date, delivery status, lock symbol #4450

Closed
RiseT opened this issue Nov 8, 2015 · 4 comments
Closed

Conversation list: Time & date, delivery status, lock symbol #4450

RiseT opened this issue Nov 8, 2015 · 4 comments

Comments

@RiseT
Copy link
Contributor

RiseT commented Nov 8, 2015

I suggest that the items within the conversation list - which at the moment just display time/date of the last message - are adjusted to exactly the same format used within the actual conversations/messages, i. e. time/date, delivery status (checkmarks) and lock symbol (if last message is encrypted).

This has a more coherent look and it's more convenient being able to check if last messages have been delivered (or read should you decide to implement an - optional, ideally even optional per contact - read status, which in my opinion wouldn't hurt) just from the conversation list.

On a sidenote, time & date of message records like "%s called you" or "Called %s" should be right-aligned like they are within the messages, and not centered like they are now. This has an incoherent look to it.

Sorry in advance if this is a duplicate - couldn't find a related issue.

@2-4601
Copy link
Contributor

2-4601 commented Nov 10, 2015

Related #3012

@jeremymasters
Copy link

Also, the message that notes the incoming or outgoing call is probably a little bit too tall which only is an issue because it reduces the amount of conversation that is visible on the screen. It also might be good to have a way to see only typed conversation, for instance, if I don't want to worry about when I made or received a signal call.

@2-4601
Copy link
Contributor

2-4601 commented Dec 19, 2015

7c95adc solved the main idea of this issue?

@RiseT
Copy link
Contributor Author

RiseT commented Dec 19, 2015

@2-4601 That's right. Wondering about this as well. I've put too many small additional issues in there (some of them still unresolved), which make it hard to resolve this 100%.

Nevertheless - closing.

@RiseT RiseT closed this as completed Dec 19, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants