Annoying bugs + Bug report

[Tarjei Knapstad]

On Fri, 17 Aug 2001, Eva Brucherseifer wrote:

>
> > > > > Actually I miss the option of the good ole 1.4 Header/Cpp/Doc tabs...
> > > >
> > > > Well, I liked that a lot as well. Sigh :)
> > >
> > > The TabPage MDI mode should fit your needs. Just close the files if you
> > > get more than 1 header or 1 cpp or 1 doc. :)
> >
> > I actually think this mode should be reintroduced. Closing the files,
> > allways keeping one is a bad option. This is not just being lazy - after
> > you've finished an invloving debugging session you typically end up with a
> > zillion files open, in which case I now use Window -> Close All. This is
> > not even a subject with the old tab mode which I think should be kept.
>
> Oh yes... debugging sessions are fatal in regard to the number of open files
> ;-)
>
> With the old mode files were kept open, but not shown. This way it was very
> fast to show another file. So the method to close files you don't want to see
> is no good option. I'd like to make it configurable how many files per type
> can be open. Something like 3 headers, 3 implementation files, one other file
> and 2 documentation files.
> Is there any reason, there is only 1 doc window allowed?
>
That's what I thought. After 1 week working on a project in Kdev 1.4
without ever closing it, it got veeery sluggish :)

Another option would be to let files autoclose after say 5 or 10 minutes,
but this is a bit more "background magic" and involves a save before close
to avoid losing data (but I guess this is allready done anyway when you
close a file.)

Just went to test this, which caused a segfault. Calling Close File on a
modified file, caused a crash after answering yes to the "do you want to
save dialog". Backtrace (seems to be QExtMdi):

=====================================================================

(no debugging symbols found)...0x411ff519 in __wait4 ()
   from /lib/i686/libc.so.6
#0  0x411ff519 in __wait4 () from /lib/i686/libc.so.6
#1  0x4126f9e4 in __DTOR_END__ () from /lib/i686/libc.so.6
#2  0x409c7eb8 in KCrash::defaultCrashHandler () at eval.c:41
#3  <signal handler called>
#4  0x40cb8d47 in QObject::queryMetaObject ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#5  0x40cb6c9b in QObject::inherits () from
/usr/lib/qt-2.3.1/lib/libqt.so.2
#6  0x4011d0a5 in QextMdiMainFrm::eventFilter (this=0x827f608,
obj=0x8684168,

    e=0xbffff040)
    at ../../../../kdevelop/widgets/qextmdi/include/qextmdichildview.h:443
#7  0x40cb74cb in QObject::activate_filters ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#8  0x40d0089e in QWidget::event () from /usr/lib/qt-2.3.1/lib/libqt.so.2

#9  0x40c68c14 in QApplication::notify () from
/usr/lib/qt-2.3.1/lib/libqt.so.2

#10 0x4092fcc9 in KApplication::notify () at eval.c:41
#11 0x40cfec20 in QWidget::setFocus () from
/usr/lib/qt-2.3.1/lib/libqt.so.2
#12 0x40c6a4e5 in QApplication::setActiveWindow ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#13 0x40c344fc in QApplication::x11ProcessEvent ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#14 0x40c333da in QApplication::processNextEvent ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#15 0x40c6ab3c in QApplication::enter_loop ()
   from /usr/lib/qt-2.3.1/lib/libqt.so.2
#16 0x40c33357 in QApplication::exec () from
/usr/lib/qt-2.3.1/lib/libqt.so.2
#17 0x080eb052 in CToolClass::writeToolConfig () at eval.c:41
#18 0x41161177 in __libc_start_main (

    main=0x80ea0f0 <CToolClass::writeToolConfig(QValueList<CToolApp> const
&)+526464>, argc=1, ubp_av=0xbffffb1c, init=0x80621a4 <_init>,

    fini=0x81fd0b0 <_fini>, rtld_fini=0x4000e184 <_dl_fini>,
    stack_end=0xbffffb0c) at ../sysdeps/generic/libc-start.c:129

====================================================================

I'm in "Childframe mode" when doing this.

> BTW, when I click on files (e.g. in childframe mode) the whole window
> flickers. It looks as if the menu bar, tool bars, etc. are refreshed. After
> some time this is quite annoying. I have the new suse rpms of kde 2.2
> installed. Has anyone else the same problem?
>
Not so under RedHat 7.1 (with the RH rpms...)

> Still I have to add here, that these are details... basically kdevelop 2.0 is
> just great :-))
>
Hmm, well, I'm just considering moving back to 1.4. This seems to unstable
yet.

-- 
Tarjei Knapstad, MSc
Head of Software Development

ChemCon AS
Professor Brochs vei 6
7030 Trondheim

Phone: +47 73 54 03 73
tarjei at chemcon.no


-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«