[master] Two more for the busied cursor

Vratislav Podzimek vpodzime at redhat.com
Thu May 9 10:39:20 UTC 2013


On Tue, 2013-05-07 at 16:32 -0400, Chris Lumens wrote:
> > I've found out that unfortunately the Gtk/Gdk switches the cursor only when the
> > main loop runs. Which means that if we want to use the busy cursor we need to
> > iterated the main loop after switching it. This is what the PATCH 1/2 does, but
> > I'm not sure if we really want to something like that. If anybody sees a problem
> > in it, maybe its better to revert the previous two patches for the busied_cursor
> > instead of applying these two.
> > 
> > PATCH 2/2 just adds the busied_cursor for environment toggling which takes a
> > while.
> 
> Ugh, I don't really like having to go back to iterating the main loop
> ourselves.  That's how pretty much everything in the old UI used to
> work, and I'm going to have flashbacks.
> 
> Note that at least for this environment toggling, a lot of the slow down
> is likely due to logging the yum lock.  Try disabling that (there's a
> commit that disables it for final releases - could just tweak that) and
> see if the slowness magically goes away.
Yeah, I realize that iterating the main loop really is not a thing we
want to do. And since I cannot make the cursor changes work without it,
instead of pushing these two I'll revert the patches that introduced
the context manager and added it to the custom spoke. If anybody finds a
way how to make it work without the main loop iterations, we can always
get it back.

-- 
Vratislav Podzimek

Anaconda Rider | Red Hat, Inc. | Brno - Czech Republic



More information about the anaconda-patches mailing list