Version: 0.98 (using KDE KDE 3.2.1) Installed from: RedHat RPMs OS: Linux If you are in MDI mode: Tab Page Mode when there is one window (tab) present, there will be a tab in the kst window with the window name in it. If you then switch to Childframe Mode, the tab is still there. If you then switch back to Tab Page Mode, the tab (and bar where the tabs live) will disappear (and I can't seem to get it back). In addition, when the tab is gone, a small 'x' button will appear, to the right of the menus (in the middle of the menu bar; note this is not the same place as where the tabs live), and this x will act like a close window button. How to reproduce: Start kst; go to Tab Page Mode; put a plot on the page; switch to Childframe Mode; switch back to Tab Page Mode. Expected behavior: The tab's shouldn't mysteriously disappear. Furthermore, the 'x' should either always be there, or never exist.
On Wednesday 14 July 2004 23:10, Matthew Truch wrote: > If you are in MDI mode: Tab Page Mode when there is one window (tab) > present, there will be a tab in the kst window with the window name in it. > If you then switch to Childframe Mode, the tab is still there. If you then > switch back to Tab Page Mode, the tab (and bar where the tabs live) will > disappear (and I can't seem to get it back). In addition, when the tab is > gone, a small 'x' button will appear, to the right of the menus (in the > middle of the menu bar; note this is not the same place as where the tabs > live), and this x will act like a close window button. > > How to reproduce: Start kst; go to Tab Page Mode; put a plot on the page; > switch to Childframe Mode; switch back to Tab Page Mode. > > Expected behavior: The tab's shouldn't mysteriously disappear. > Furthermore, the 'x' should either always be there, or never exist. I think these are KMDI bugs actually. I'll investigate later. Curious, do you see this problem with KDevelop or Quanta? We share KMDI with them.
I never use KDevelop or Quanta, and can't figure out how to change the MDI modes explicitly. Everything I tried did not cause a bug like in kst, but I'm not sure I was changing anything appropriate.
It seems to be in the 3.1 compat library we ship w/ kst. My MDI experience became much less .... "rich" (in the way you are describing) when I upgraded to a newer kde. cbn On July 14, 2004 11:27 pm, Matthew Truch wrote: > ------- You are receiving this mail because: ------- > You are the assignee for the bug, or are watching the assignee. > > http://bugs.kde.org/show_bug.cgi?id=85224 > > > > > ------- Additional Comments From matt truch net 2004-07-15 05:27 ------- > I never use KDevelop or Quanta, and can't figure out how to change the MDI > modes explicitly. Everything I tried did not cause a bug like in kst, but > I'm not sure I was changing anything appropriate. > _______________________________________________ > Kst mailing list > Kst@kde.org > https://mail.kde.org/mailman/listinfo/kst
Ok, if it's our compat library only then I think it's not worth the effort to fix. 3.1 users: time to upgrade to KDE 3.2. 3.3 is out in a month! :)
I rebuilt on a machine with 3.2, but the bug still exisits; however I'm not so sure it isn't still trying to use the compat library. How would you tell which libraries it's using (aka which library is kmdi in)?
If you do a make clean, does it build libkstkmdi/*.lo files? Does ldd `which kst` show: libkmdi.so.1 => /opt/kde3/lib/libkmdi.so.1 (0x0fe3a000) or similar?
make clean && make *does* build libkstkmdi/*.lo files, and ldd `which kst` shows no libkmdi.so.1 file (which is how I first checked for kmdi linking, but wasn't sure what the name of the .so was).