If a long-running bkup routine is running, moving to another workspace causes the EZ-Bkup window to be all grey/black or have graphical artifacts that "cover" the whole window. The proper EZ-Bkup window contents/widgets eventually come back once the Bkup routine (running of rsync) finishes.
rsync processes are currently run on the main thread. This blocks the gui from updating until they are done. rsync processes must be called on their own thread or via async to prevent this.
If a long-running bkup routine is running, moving to another workspace causes the EZ-Bkup window to be all grey/black or have graphical artifacts that "cover" the whole window. The proper EZ-Bkup window contents/widgets eventually come back once the Bkup routine (running of rsync) finishes.
rsync processes are currently run on the main thread. This blocks the gui from updating until they are done. rsync processes must be called on their own thread or via async to prevent this.
If a long-running bkup routine is running, moving to another workspace causes the EZ-Bkup window to be all grey/black or have graphical artifacts that "cover" the whole window. The proper EZ-Bkup window contents/widgets eventually come back once the Bkup routine (running of rsync) finishes.
rsync processes are currently run on the main thread. This blocks the gui from updating until they are done. rsync processes must be called on their own thread or via async to prevent this.
graphics issue when moving focus to another workspaceto rsync running on main thread blocks GUI 2 years agothis is also why the Bkup's Status label is not being updated as the Routine is run.
fixed in 0.9.2