DocumentSwitcherPluging are broken by workingsets
Andreas Pakulat
apaku at gmx.de
Thu Jun 25 19:33:48 UTC 2009
Hi,
See https://bugs.kde.org/show_bug.cgi?id=197870
It seems that the introduction of workingsets breaks some of the
assumption that the documentswitcherplugin has (at least thats the only
way I can see that view->document() returns a broken pointer). At least
it seems that the list of views it keeps isn't properly updated when a
workingset hides itself.
As I have absolutely 0 idea how the workingset stuff is implemented, I'm
going to need some help to fix that one. Currently the plugin is
notified when a new mainwindow is added and on each mainwindow it
connects to these signals:
areaChanged
activeViewChanged
viewAdded
aboutToRemoveView
so its notified whenever the current view changes and when the area
changes. I'm guessing that I'll need a new signal to connect to when the
workingset is changed, which one?
Also what consequences does disabling a workingset have, i.e. does it
close all connected documents? Does it just remove all views? If the
latter why is aboutToRemoveView never emitted.
Andreas
--
Troubled day for virgins over 16 who are beautiful and wealthy and live
in eucalyptus trees.
More information about the KDevelop-devel
mailing list