[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kmail-devel
Subject:    [Bug 49784] strange question marks left to subject
From:       Stefan Bittner <sbi () pobox ! com>
Date:       2002-10-29 0:04:26
[Download RAW message or body]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=49784     




------- Additional Comments From sbi@pobox.com  2002-10-29 01:04 -------
Subject: Re:  strange question marks left to subject

On Monday 28 October 2002 22:59, you wrote:
snip...
> >
> > IMHO in that line you should display the state of the message and
> > not the state of Your knowledge of the message.
> > The message has any of the encrypted / signed / not encrypted / not
> > signed state and that state definitely doesn't change because one
> > selects ist. It's just that You now more about the mail once it's
> > selected.
>
> Let me reiterate:
> When nothing is shown then this indicates that the message it neither
> signed nor encrypted.
> When the signature/lock icons are shown then this indicates that the
> message is partially/fully signed/encrypted with/without problems.
> Last but not least, when questions marks are shown this indicates that
> it's currently unknown whether the message is signed and/or encrypted.
>
> We can't simply show nothing when the state of a message is unknown
> (because it hasn't been checked yet) because then the user would
> correctly assume that the message is _not_ signed and _not_ encrypted
> which is not necessarily the case.
>

I suppose the user happily accepts that until the message is not selected 
there is simply no_information shown about the encryption state. (At least I 
would)
And I'd prefer to have the same icons for not encrypted/not signed and 
unknown.
These question marks just draw more attention than they should.
On the other hand when it is known that the message is encrypted and/or signed
ist is "nice to have" the icon that reflects this state.


> > But as a user I'm less interested in how much knowledge KMail gathers
> > about the mail depending on if it is selected or not.
> >
> > I'm interested in the state of the message itself.
>
> Exactly. But as long as KMail hasn't checked the state of a message it
> obviously can't tell you the state. And therefore it displays question
> marks to indicate that the state is still unknown. BTW, the state of a
> message is saved in the index once it has been checked. So it will be
> only checked the first time the user selects the message and not each
> time.
>
> > The message changes only state when i decrypt or verify it.
> > So there should be state changes like encrypted->decrypted,
> > signed->verifed if You really want them.
>
> Huh? No message ever changes it's state. Messages are only decrypted to
> view them. They are not written to disk in decrypted form. This means
> their state will never change from encrypted to decrypted. The same is
> true for signed messages. The signature will never be removed so they
> will always stay signed.

But that's implementation detail. Of course the message changes state. You 
just don't persist it.
If i click on an encrypted message I see no body until I dont decrypt it or
i see the ascii armor if I can't provide a key.
When I decrypt it i see the plain text.
You call that the same state ?

>
> If you don't want those icons then please turn them off.
>

Yeah, I guess I'll have to since having the icons the way I want them is 
- as I said above - more or less "nice to have" to me.

But once we're on it:
Can You send me the source location so I can more easily patch the behaviour ?

Thanks,
Stefan
_______________________________________________
KMail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail
[prev in list] [next in list] [prev in thread] [next in thread]