https://issues.apache.org/ooo/show_bug.cgi?id=122406
Andre <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Issue Type|DEFECT |ENHANCEMENT --- Comment #1 from Andre <[email protected]> --- I am changing the issue type to enhancement. I agree that a form of caching might improve usability in a few cases but the state of most panels is defined by items which belong to the document and therefore is already persistent. Adding caching will open its own can of worms. I did not implement caching of panels because: - No premature optimization. - In the beginning the Impress panels where still tied to view shells. Caching them would have been a major undertaking. - We don't have a performance problem (to my knowledge). - Panels in the cache still need some parent window. Changing parents of controls that are not designed for that may or may not work. - Caching panels of unknown implementation and complexity may require a good caching strategy to avoid allocating too many resources. - Most panels are not designed to be dormant for an extended period of time. They may have listeners and might react to events which can lead to unexpected results. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.
