Comment 2 for bug 17138

Thanks for your bugreport.

This is problematic both from a technical POV as well as from a usability POV.
The problem is that certain operations change the state of the system. A update
operation can e.g. update the description of a package. How should the UI react
when this happens? Just silently change the text? Or ask the user to confirm
that the view needs to be updated? The same is true for install/removals, this
changes filters and views.

The only option I see is that the stuff (update, download, install/remove) is
happening in the background and that the ui is updated at the point when the
operation is finished (we can't avoid the delay when the cache is build). The ui
can then try to preserve the users view and selections as much as possible.

What do you think?

Cheers,
 Michael