https://bugs.kde.org/show_bug.cgi?id=461749
--- Comment #8 from jesse ---
Yes, I think the clean up of data structures and such should be left to the
developers to figure out and engineer the best solution. From a user
perspective though, I think it makes senses that the user should be allowed to
https://bugs.kde.org/show_bug.cgi?id=461749
--- Comment #7 from Jack ---
Displaying a "Cancel" button is trivial. Having a button on the Configure
dialog that totally closes the report without generating results is probably
not difficult. However, creating a button on the report (not just on th
https://bugs.kde.org/show_bug.cgi?id=461749
--- Comment #6 from jesse ---
Why not put a cancel button and if the cancel button is pressed, do not
generate the report and close the dialog?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=461749
--- Comment #5 from Jack ---
This does work, but if I open the config dialog for a report I decide not to
modify, there is no way to close the report quickly, since closing the config
dialog starts the complete report generation. I know I could modify
https://bugs.kde.org/show_bug.cgi?id=461749
Thomas Baumgart changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=461749
--- Comment #3 from jesse ---
Ok. I see. I think it should wait to generate the report until the configure
dialog is closed or Apply is pressed by the user.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=461749
--- Comment #2 from Jack ---
The problem right now is that you CAN right click on the report name and
select Configure, but it runs the full report before displaying the configure
dialog. Going straight to the dialog first would be a good solution.
-
https://bugs.kde.org/show_bug.cgi?id=461749
jesse changed:
What|Removed |Added
CC||jvap...@yahoo.com
--- Comment #1 from jesse ---
Anothe
