* origin/pr/167:
More documentation and added another column for default_dispvm to Qube Manager
Added DVM Template column to Qube Manager
Rewritten Qube Manager widgets
In rare case (when the Qube Manager was reverted to an older version
that does not have a column on which it was last sorted) downgrading
Qube Manager could result in a crash on start.
* origin/pr/154:
Fix too long lines
Moved busy_cursor() inside save_changes()
Removed unneded calls to Override/Restore cursor
Removed duplicated call to save_changes()
Removed unneeded Cursor override/restore
Added busy_cursor()
Added BusyCursor for notify manager is working
Revert "Added progress bar to __save_changes__"
Revert "Increase progress wait time to 2s"
Increase progress wait time to 2s
Added progress bar to __save_changes__
Remove unneeded slot connections and reject overwrite
* origin/pr/132: (48 commits)
Fixed unreachable code thanks to travis
Clear searchbox pressing esc without need of selecting it
Fix errors when some domain fails to start
wait thread to finish when aborting
Don't terminate backup thread when aborting
Fix iterating and removing over list
Use 'qube' instead 'Qube'
Qube -> qube
Catch possible KeyError when starting dispVM
Fix authorship and python version
Create backup_window on the stack
Removed sigchld_handler old code
Fix pylint
Do not terminate the thread
Fix error/success message on dialog
Fix opening settings/boot dialog after VM creation
Add pylint disable too-few-methods
Fix travis errors
Removed unused import
Workaround for backup dialog modeless behaviour
...
Otherwise it can casue an error:
RuntimeError: wrapped C/C++ object of type QProgressBar has been deleted
at line 1277
of file /usr/lib/python3.5/site-packages/qubesmanager/qube_manager.py.
I don't know how to avoid it.
Since now it's modeless, user could have already it opened
but we have to destroy it and recreate when closed for vm list
being refreshed (at least for now)
Simple design and better performance, just start() thread and finished
call back will show any error or msg, stop progress dialog and do cleanup.
Full remove of QT process_events() calls.
This is the recommended QT way for updating the progress bar.
setMininumDuration() sets the time when the progress dialog will appear,
if it finishes before it won't be shown. Qt default is 4 seconds, maybe
pretty high for this case.
I am not sure what this wants, but it seems that doesn't affect
xfce but on kde does the progress bar appear randomly in the screen
without it on both cases it appears at center of screen
