Bug 87599 - progress status not shown anymore
Summary: progress status not shown anymore
Status: RESOLVED FIXED
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.7
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-08-20 14:04 UTC by Leo Savernik
Modified: 2009-12-19 23:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leo Savernik 2004-08-20 14:04:27 UTC
Version:           1.7 (using KDE 3.3.0, compiled sources)
Compiler:          gcc version 2.95.2 19991024 (release)
OS:                Linux (i686) release 2.4.24

In KDE 3.2, when fetching mails, KMail displayed the progress status in the status bar in the form of "Fetching message %1 of %2 (%3 of %4 KB) from %5", neatly updating it while downloading the mails.

In KDE 3.3, this has disappeared. It only says at the beginning "Checking account %1 for new mail", then starts downloading *without* displaying the progress message, then says "Transmission for account %1 complete."

This is a really nasty regression that should be fixed.

(Btw, the progress bar at the right hand side of the status bar is not affected, and hence not covered by this bug.)
Comment 1 Anders E. Andersen 2004-08-23 14:25:08 UTC
Hmm.. This works for me.. I think.. Mostly at least.

The progress status does seem to disappear from time to time, and then appear again showing more mails fetched. Sometimes when it is half done it will disappear and then after a while it will indicate it is fully done and that fetching mail has ended. So I guess it is a bit dodgy.

Could this change have anything to do with work being done to thread the mail fetching process. Currently that freezes the gui, which is one of the most popular kmail bugs (if not the entire kde). See Bug #41514.

P.s. You might want to vote for your bug, if you want to see it fixed.. :)
Comment 2 Leo Savernik 2004-08-23 14:46:27 UTC
Do you have a fast connection? I'm temporarily having a fast connection, and it doesn't seem to be that noticeable. Though at home through modem, I never see any progress status messages.

And yes, voting can't hurt :-)
Comment 3 Leo Savernik 2004-08-23 15:00:10 UTC
Asking Ingo, he told me that the detailed status information has been shelled out to an information window. I think that's a viable compromise I can live with.

Hence, closing.
Comment 4 Anders E. Andersen 2004-08-23 15:24:36 UTC
I think a fast connection and a fast system does help with getting it updated more regularly. I have cel650 with 300meg ram and 256/256 connection.
Comment 5 Leo Savernik 2004-09-01 15:48:33 UTC
Reopening this bug. I've detected that continuously expanding the progress popup is actually a usability nuisance. I therefore propose that either

- bug 88591 is implemented.
- the progress popup is still shown in the status line, whereas manually issued fetch jobs always take priority over automatically scheduled fetch jobs.
Comment 6 Till Adam 2004-09-02 14:39:28 UTC
Leo, you've created 88591, which I think is a reasonable suggestion. Why do you open this bug report, though? If as you say yourself implementing it would solve your problem, this one is at most a duplicate. Please consider closing it again, I don't see much point in cluttering b.k.o with many versions of the same problem.
Comment 7 Leo Savernik 2004-09-02 15:47:48 UTC
I changed my mind in reopening this because daily usage has shown that not having the progress status in the status bar provides too little information.

OTOH, having the progress popups opened covers too much of the preview area (so reading text at the bottom of emails is prevented, especially if there is more than one fetch job), resulting in usability degradation.

To clarify, I filed bug 88591 when I thought it would suffice. Now I don't consider it to be a "must have", so feel free to close it as wontfix if it's too much burden. I think fixing this bug is much more important usability-wise.
Comment 8 Björn Ruberg 2009-12-19 23:16:16 UTC
I see this fixed in current kmail