| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
* log when threads are started and are finished
* log progress messages
* log all the running threads and their stack frame when USR2 is
received.
|
| |
|
|
|
| |
We need this to quit when handling errors, since doing a sys.exit() from a
thread only kills the thread and not the main program.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
With the previous code, I could never get the UI to be redrawn to reflect the
changes, even though the changes appeared to have taken effect.
This new code instead uses a message queue for communication between the thread
doing all the hard work and the main thread that handles GTK stuff. The storage
code will shove messages into that queue when it does something like create a
filesystem, and the main thread watches in the idle loop for messages.
I've also provided yet another context manager to make all this code simpler.
|
| |
|
|
|
|
|
| |
We need to be able to update the progress bar and the message independently.
The message should be updated when an action begins so you know what's
taking so long, and the progress bar should be updated when an action ends
so you know how far you are through now.
|
|
|
It consists of a very basic ProgressReporter class and singleton that serves
as a wrapper around the UI implementation so anaconda doesn't need to know
what kind of interface is running, and then a couple methods in the existing
GUI progress bar class to set things up.
|
