Smart should also display a "Saving cache..." msgbox when exiting

[David Smid]

Smart should also display a "Saving cache..." msgbox when exiting because users are confused about the fact that the main window isn't closed immediately (they usually can't notice the message in status bar).

http://issues.unity-linux.org/index.php?do=details&task_id=293

[David Smid (dsmid)]

Possible implementation in lp:~dsmid/smart/saving-cache-msgbox

[Anders F Björklund (afb)]

This is especially visible when using rpm-md, since the cache is so big there...
But the fix should probably be in the right place, i.e. with the original message ?
smart/control.py:202: iface.showStatus(_("Saving cache..."))
smart/control.py:254: iface.showStatus(_("Loading cache..."))

I made an implementation that shows a progressbar, but it was 10x slower (!).
So the best would be to add support for "infinite" progressbars, and use that:
http://www.pygtk.org/docs/pygtk/class-gtkprogressbar.html#method-gtkprogressbar--pulse
http://doc.trolltech.com/3.3/qprogressbar.html#totalSteps-prop (i.e. setting totalSteps to 0)

[Anders F Björklund (afb)]

Not sure about the progressbars, so delaying everything to the interface overhaul.

[Robert Xu (bravoall1552)]

I know this is an old bug, but I'm annoyed by the saving cache dialog.
The "OK" button on it doesn't make sense, and the whole GUI freezes up...
(This is on Unity, btw)
Isn't it better to show the message in the status bar, like where the "No interesting upgrades available!" show?

[Anders F Björklund (afb)]

Re Comment #5: Showing the message in the status bar (only) is the original behaviour...

[Robert Xu (bravoall1552)]

I'd rather have that happen... Even in patch form, I'm ok, because then I can just use the patch.

[Anders F Björklund (afb)]

If you don't want the dialog happen, then don't apply the (unity) patch... ?

The best would be if the dialog would only show after an extended period of time, or if the progress bar actually reflected the pickling/unpickling progress. But that is either tricky to get right, or actually slows down the process tenfold. So the best would probably be to show the inifinite progress, and switch show-status to show-progress (using both looks strange in the text interface). Either way, it shouldn't be done in the gtk implementation only.