-
Notifications
You must be signed in to change notification settings - Fork 106
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
Allow toggle between default view and conversation view #395
Comments
Hi, While this is an often-requested feature, it is likely not to be implemented. This would make things extremely complicated, and the goal of Thunderbird Conversations is to provide a suitable alternative to the message reader. I'd rather have you explain why you still have to go back and forth rather than provide you with a way to disable, even temporarily, the conversation view. Return receipts won't be implemented in the near future, although this is an easy bug, so you're welcome to tackle it. I could provide directions if you're interested. Toolbar buttons already provide a lot of functionality. What is it you're missing exactly? |
The toolbar buttons aren't too important, I just thought the keyword-button would be nice to have to quickly tag a single message and not the whole conversation. |
hi, |
Hi there, See #129 for There are two codepaths: for messages that are streamed Then, you need to re-implement the logic for sending the status delivery notification. You need to imitate:http://mxr.mozilla.org/comm-central/source/mailnews/extensions/mdn/src/nsMsgMdnGenerator.cpp#1052
Feel free to ask for more guidance on Cheers, Jonathan The steps would be as follows:
~ jonathan On 12/13/2015 03:36 PM, alexrah wrote:
|
I'd like to have a hoktey and a button on each message in conversation view that allows me to toggle between the default message display and the conversation view. This will be very helpful while there are still actions and information in the default view which is not displayed in the conversation view. (eg return receipt requests, toolbar buttons, etc)
The text was updated successfully, but these errors were encountered: