https://bugs.documentfoundation.org/show_bug.cgi?id=151167

            Bug ID: 151167
           Summary: All potentially very long operations should be
                    cancellable.
           Product: LibreOffice
           Version: unspecified
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: medium
         Component: UI
          Assignee: [email protected]
          Reporter: [email protected]

Description:
In any LO application, the user should be able to cancel any operation that
could reasonably take a very long time – 5 minutes or longer on a slow machine.
Around once or twice a week I manage to accidentally press some key combination
that changes the cursor to the "wait" state and locks up the application.  I
have also experienced the related bugs #48701 (abort loading of a file) and
#148407 (cancel an ongoing paste).
I was tempted to file this as a bug rather than a feature request: if an app
hangs, it's a bug.  And if the user has no idea how long the operation will
take, then after a certain time threshold (several minutes), it's effectively
hung from the user's persepective.  Requiring some sort of progress bar for
long operations would also be a great help.
Killing the process is a poor substitute, for a variety of reasons, including
lost work in whatever documents are open (I usually have many open).

Steps to Reproduce:
1. Start an operation that's going to take several or many minutes to complete.
2. Try to cancel it – there isn't any way.

Actual Results:
I have to kill the LO process.

Expected Results:
Pressing the ESC key cancels the operation, or perhaps invokes a dialog
confirming that I want to cancel.  Or clicking a button the the status bar.


Reproducible: Always


User Profile Reset: No



Additional Info:
I didn't have any Other Information, but if you insist ...
There's a number of ways this could be implemented, including:
a) Each long operation polls some logical status flag that indicates if the
user requested cancelling.  Probably not the most reliable approach, though
perhaps the cleanest.
b) Each long operation runs in its own thread, leaving the LO UI alive, though
possibly temporarily disabling editing operations in the active document. 
Hitting the cancel button (or ESC or whatever) kills the thread.  Probably not
the cleanest approach, though perhaps more reliable.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to