[Kst] MDI Modes

[George Staikos]

Ah the first KDE 3.1 victim. :-)  Ok does it help if you change $(LIB_KIO) to 
$(LIB_KPARTS) in kst/kst/Makefile.am?

On Monday 26 April 2004 09:10, C. Barth Netterfield wrote:
> Can't compile...
>
> Fresh checkout from cvs gives, after link stage of make:
>
> ./.libs/libkst.so: undefined reference to `virtual thunk [v:0,-12] to
> KParts::DockMainWindow::~DockMainWindow [in-charge deleting]()'
> ./.libs/libkst.so: undefined reference to `KParts::PartBase::~PartBase
> [not-in-charge]()'
> ./.libs/libkst.so: undefined reference to `virtual thunk [v:0,-12] to
> KParts::DockMainWindow::~DockMainWindow [in-charge]()'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::qt_property(int, int, QVariant*)'
> ./.libs/libkst.so: undefined reference to
> `KParts::PartBase::PartBase[not-in-charge]()'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::className() const'
> ./.libs/libkst.so: undefined reference to `virtual thunk [v:0,-40] to
> KParts::PartBase::setInstance(KInstance*)'
> ./.libs/libkst.so: undefined reference to `virtual thunk [v:0,-16] to
> KParts::DockMainWindow::~DockMainWindow [in-charge deleting]()'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::qt_invoke(int, QUObject*)'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::qt_emit(int, QUObject*)'
> ./.libs/libkst.so: undefined reference to `virtual thunk [v:0,-16] to
> KParts::DockMainWindow::~DockMainWindow [in-charge]()'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::qt_cast(char const*)'
> ./.libs/libkst.so: undefined reference to `typeinfo for
> KParts::DockMainWindow'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::slotSetStatusBarText(QString const&)'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::staticMetaObject()'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::~DockMainWindow [not-in-charge]()'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::~DockMainWindow [in-charge]()'
> ./.libs/libkst.so: undefined reference to
> `KParts::PartBase::setInstance(KInstance*, bool)'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::DockMainWindow[not-in-charge](QWidget*, char
> const*, unsigned)'
> ./.libs/libkst.so: undefined reference to
> `KParts::PartBase::setInstance(KInstance*)'
> ./.libs/libkst.so: undefined reference to `KParts::PartBase::~PartBase
> [in-charge deleting]()'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::~DockMainWindow [in-charge deleting]()'
> ./.libs/libkst.so: undefined reference to `KParts::PartBase::~PartBase
> [in-charge]()'
> ./.libs/libkst.so: undefined reference to
> `KParts::DockMainWindow::createShellGUI(bool)'
> ./.libs/libkst.so: undefined reference to `virtual thunk [v:0,-12] to
> KParts::PartBase::~PartBase [in-charge deleting]()'
> ./.libs/libkst.so: undefined reference to `typeinfo for KParts::PartBase'
> ./.libs/libkst.so: undefined reference to `virtual thunk [v:0,-12] to
> KParts::PartBase::~PartBase [in-charge]()'
> collect2: ld returned 1 exit status
> make[2]: *** [d2asc] Error 1
> make[2]: Leaving directory `/home/cbn/programs/KDE/kdeextragear-2/kst/kst'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/cbn/programs/KDE/kdeextragear-2/kst/kst'
> make: *** [all-recursive] Error 1
> aragorn [~/programs/KDE/kdeextragear-2/kst]>
>
> On Sunday 25 April 2004 4:04 pm, George Staikos wrote:
> > As you saw from my last commits, Kst is now using KMDI, which means Kst
> > is horribly broken in HEAD until we switch to using the new view code. 
> > It would be a huge effort to port the old view code over because it is
> > assumed all over the place that there is only one view.  Meanwhile, I
> > added some actions to the settings menu so that everyone can experiment
> > with the different MDI modes.  We have smoe advantages with childframe
> > mode in that the central widget is available for us to use as we like. 
> > I'm thinking it might be a good place to put the data manager even. 
> > Barth mentioned that he liked the idea of tabbed mode.  Does anyone have
> > strong feelings about this?  Should I leave it selectable even (with a
> > proper action of course)?
> >
> > The next trick becomes how to deal with all of our actions and "modes".
>
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst

-- 
George Staikos
KDE Developer				http://www.kde.org/
Staikos Computing Services Inc.		http://www.staikos.net/