Summary: | UI: Warning when applying Autoformat > Styles for a large (empty) range | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | Telesto <telesto> |
Component: | Calc | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | UNCONFIRMED --- | ||
Severity: | enhancement | CC: | eyalroz1, heiko.tietze |
Priority: | medium | ||
Version: | 24.2.0.0 alpha1+ | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Crash report or crash signature: | Regression By: |
Description
Telesto
2023-12-08 19:31:17 UTC
So, why am I CCed? :-) (In reply to Eyal Rozenberg from comment #1) > So, why am I CCed? :-) Well mostly because of your idea's/opinions/suggestions on plenty of topics and the ability of expressing those clearly. Or put it differently I appreciate your view.. But well it's totally voluntary.. If so say, I'm uninterested, also fine. But well I should probably added the question: options? instead of blank cc > If you apply autoformat -> styles LibreOffice will Freeze/hang for long time
This is the problem. Why can't we interrupt such operations while they're ongoing?
There are are operations which could potentially take a long time; like - parsing a huge input CSV for example.
In general, lengthy operations should have a feedback (hourglass, throbber, progressbar, etc.) or run in the background (with the opportunity to cancel). Just telling the user that something might have negative consequences is not actionable. For example, on some systems your example could take hours to finish and on other some seconds. And it's very difficult to predict. (In reply to Heiko Tietze from comment #4) > In general, lengthy operations should have a feedback (hourglass, throbber, > progressbar, etc.) There might already even be a progress indication in this case, although this must be verified of course. The thing is, we have to let the user understand that the overall time might be exceedingly high. And, like I said, let the user abort. |