https://bugs.kde.org/show_bug.cgi?id=461749
--- Comment #8 from jesse <jvap...@yahoo.com> --- 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 configure the report without the need for the report to execute first. This would keep the issue you are reporting from happening. I have not personally ran into it as my data size is very low. But one day I will face this. I believe, from a user perspective, it would be ideal if I can open a configuration for a report, and decide after configuring it if I want to : 1. Cancel - disregard the changes and stop the report execution. Return the user to the list of reports to choose from. 2. Apply - Apply the changes to the report but do not execute the report. Return the user to the list of reports to choose from. 3. Run - Apply the changes to the report and execute the report generation. This would result with three options for the user in the report configuration dialog box. -- You are receiving this mail because: You are watching all bug changes.
