https://bugs.kde.org/show_bug.cgi?id=410548
Bug ID: 410548
Summary: Feedback in kis_delayed_save_dialog on the stroke that
is blocking save.
Product: krita
Version: git master
Platform: Other
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Usability
Assignee: krita-bugs-n...@kde.org
Reporter: griffinval...@gmail.com
Target Milestone: ---
SUMMARY
I am noticing that I come across the delayed save dialog far more often when I
am using the appimage than when I'm using my own build.
To identify what is causing this, I would like to see the actual actions that
cause this behaviour. Theoretically, we should be able to get human friendly
info from the kis_strokes themselves, they have a string for the undo command.
However, I don't know enough about the update scheduler to try and hack it so I
could get information about the stroke(s) it is currently processing.
Furthermore, that information then needs to be funneled through kis_image
before kis_delayed_save_dialog can access it.
Given that I am seeing that the update scheduler seems to be able to track how
many jobs it's still processing, maybe we should use that kind of information
too for the delayed_save_dialog.
I think this would benefit user feedback in general.
--
You are receiving this mail because:
You are watching all bug changes.
