https://bugs.kde.org/show_bug.cgi?id=337891
--- Comment #5 from Alexander Dymo <ad...@kdevelop.org> --- This can be done only as a hack. The whole architecture is built with an assumption that different areas will have different set of editor and tool views. The place to hack it is probably MainWindow::setArea in sublime/mainwindow.cpp. You'll have both old and new area objects. Then you'll need to: - remove all "views" (not the "toolviews") from the new area (in case there are views there from previous switch) - traverse all views in the old area and ask their documents to add views to the new area (make sure to do this in a tree-like fashion to preserve split window configuration, Area::walkViews is the way to do this) I think I'd do this after line #121 HoldUpdates hu(this); This hack is not too bad for production use. View creation is super fast. And this won't actually create any KTextEditor::View instances until they need to be displayed on the screen. -- You are receiving this mail because: You are watching all bug changes.
