https://bugs.kde.org/show_bug.cgi?id=472334
--- Comment #13 from Igor Kushnir <[email protected]> --- (In reply to John Sennesael from comment #12) > Currently a 'window' is basically holding the entire application state, and > that all would have to be moved into a proper application class, with a > fairly minimal window/editor class holding only the state needed for editing > whatever tabs are open in it. I don' think this is the case. There are many controller classes, which are shared among all main windows. I believe each main window should have (as it does already) its own view containers, document views and tool view widgets. I'm going to create a merge request that shares tool view widgets between areas (code/debug/review) soon. But since ToolDocument instances are owned by the UiController, a QHash<const QMainWindow*, ToolViewWidgetData> would have to be stored in ToolDocumentPrivate to give each main window separate tool view widgets and even distinct sets of tool views. -- You are receiving this mail because: You are watching all bug changes.
