Bug 510730 - Some UI flickeryness
Summary: Some UI flickeryness
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-packagekit
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Richard Hughes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: fitandfinish
TreeView+ depends on / blocked
 
Reported: 2009-07-10 13:43 UTC by Matthias Clasen
Modified: 2009-07-21 11:26 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-21 11:26:36 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Matthias Clasen 2009-07-10 13:43:38 UTC
gpk apps have this habit of temporarily putting large parts of their ui into insensitive while the daemon does something - for instance in gpk-repo after toggling a repo, or in gpk-application, when selecting a different package.

This gives a really jarring, flickery ui experience. In general, it would be much better to try and deal with things async. E.g. there should be no need to wait for all repo metadata to be downloaded before allowing the user to make further repo changes. And likewise, the fact that the package details have not been filled in yet should not prevent the user from interacting with the package list.

Comment 1 Richard Hughes 2009-07-15 12:50:41 UTC
gpk-repo should be fixed -- the interaction is now smooth with no flickering at all:

commit 9f8ba89a975b4d09bfce3520394c295870d620e9
Author: Richard Hughes <richard>
Date:   Wed Jul 15 13:48:50 2009 +0100

    Don't flash the gpk-repo UI when we enable or disable repos. Fixes half of rh#510730

I'll work on gpk-application when I get a few minutes.

Comment 2 Richard Hughes 2009-07-21 11:26:36 UTC
commit 75880f2ef691edbab2e0d68faf119332c2dc6fab
Author: Richard Hughes <richard>
Date:   Tue Jul 21 12:25:07 2009 +0100

    Don't set the package view insensitive when doing searches, and add a delay to prevent flicker. Fixes rh#510730


Note You need to log in before you can comment on or make changes to this bug.