[Users] [Bug 3297] mark thread read

[blind Pete]

On Mon, 13 Oct 2014 20:37:52 +0000
noreply at thewildbeast.co.uk wrote:

> http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=3297
> 
> Paul <paul at claws-mail.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>            Severity|normal                      |enhancement
> 
> --- Comment #1 from Paul <paul at claws-mail.org> ---
> "this one-selected-line represents all messages in the thread because
> it is folded" is purely your own interpretation.

This is a User Interface design question.  

The UI should be simple, clear and unambiguous.  If there is any need, 
or even possibility, of interpretation, then there is room for
improvement.  

Now the hard part; can I think of anything that would be any better?  

Just brain storming...  

*)  The first menu box pops up with
    message options =>
    thread options  =>

*)  The current menu pops up with an extra entry at the bottom
    blah
    blah
    thread operations =>

*)  Separate entries for ambiguous options
    blah
    blah
    mark message 
    mark thread
    etc.

*)  Sub menu when relevant 
    mark => message
            thread

*)  Keep the existing functionality, but change the menu 
    entry from "mark" to "mark message".  

When there is only one message, don't offer any thread options.  

-- 
testing
bP
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.claws-mail.org/pipermail/users/attachments/20141014/650c5468/attachment.sig>