| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
| |
It also works better, in that using new_devices means when the last of the
autopart-created set is deleted, we know to re-display the CreateNewPage.
|
| |
|
|
|
|
|
| |
This also has the effect of making sure the RHS has something relevant
displayed in it after the filesystem is deleted.
|
| |
|
| |
|
|
|
|
|
|
| |
- Fix a typo
- Enable remove button for devices
- Fix a tb on removal of unused devices
|
| |
|
| |
|
|
|
|
|
| |
If autopart is selected, we re-run clearpart and autopart on apply.
If not, we do neither.
|
|
|
|
|
|
|
|
|
| |
Unset autopart flag after running ksdata.autopart.execute since we
are still techically doing custom partitioning.
Don't show devices queued for removal in the custom spoke.
Don't include Roots whose root device has been queued for removal.
|
| |
|
| |
|
|
|
|
|
|
| |
With the viewport there, the UI does not scroll automatically with keyboard
navigation. The result is that if you keep pressing the down arrow, you
eventually run off the bottom of the visible UI.
|
|
|
|
|
| |
This is a hint that we're still doing something, even if an individual step
takes a long time.
|
|
|
|
|
| |
Otherwise, the protocol drop down will start out sensitive no matter what
source we are using.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This requires a little reorganization of the deletion code to make it reusable.
It also still goes through the confirmation dialog so the user has a choice to
think about what they're doing.
Note that it still doesn't cause a now-empty page to be removed (you can get
into that situation by removing everything yourself anyway), nor does it cause
anything useful to be displayed on the RHS, nor does it put back the
CreateNewPage if you delete the autopart-created installation.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This way, it looks highlighted when you come back to the hub just like if
it was selected with the keyboard, and keyboard navigation will start on
the spoke that was just visited.
|
|
|
|
|
| |
We don't remove the empty containers unless we are the ones removing
the last device that uses them.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Only include non-existent unused devices in the "New ..." root.
Simplify removal of devices by unifying the code and always calling
storage.destroyDevice, which can handle non-existent devices as well
as existing ones.
Unused devices have no root. That is handy for identifying them from
inside the removal callback.
|
| |
|
|
|
|
| |
We need to run these before the progress hub so we can catch errors.
|
| |
|
|
|
|
|
|
| |
Since most of the accordion functions operate based on a page title, it makes
sense to have some way for users to get the title without having to root
around in gtk for it.
|
|
|
|
|
| |
This is largely just copy & paste from what msivak did elsewhere.
Thanks.
|
|
|
|
|
|
| |
We need to make the label high enough for languages
that have higher characters. The font type and size
is hardcoded so it should not change.
|
|
|
|
|
|
|
|
|
|
| |
This fixes the resizing of the language view,
because of different label lengths caused by
different translations.
It still jumps up and down, because some languages
have characters with bigger height. I had no
success with fixing that part. Nothing helps.
|
| |
|
| |
|
|
|
|
|
| |
This should fix
http://www.redhat.com/archives/anaconda-devel-list/2012-June/msg00166.html
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The Queue poll inside the GLib idle state was causing 100% CPU usage, it
was being called multiple times per second. It would be more efficient
to be able to use a select() or poll() with the Queue, but that isn't
possible. So, run the Queue processing in a 1 second timeout. CPU usage
drops to almost nothing.
Also add a call to q.task_done() for unrecognized messages.
|
| |
|
|
|
|
|
|
| |
chronyd doesn't change the time immediately because it wants to
prevent time leaps. However this way it may look like if NTP was
not running at all, so we need a manual sync first.
|
| |
|
| |
|
|
|
|
| |
These don't do anything yet, of course.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This means that when you press up and down with the keyboard to navigate the
accordion, whatever MS you hit will be the one displayed on the right, and
whatever one you were previously on will have its changes saved.
This is different from how DiskOverviews and SpokeSelectors work, but I think
it makes sense. When you keyboard to a DO, you are choosing to do include it
in the install. We don't want people doing that by accident. When you
keyboard to a SS, it would jump you into the spoke and that wouldn't work
at all. The MS, however, just changes what's displayed on part of the screen.
|
| |
|
|
|
|
|
| |
I still haven't found a need for this, and it's getting confusing with a
current selector here and a separate one in custom.py.
|
| |
|