[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    RE: newtoolbar-0.3 floats
From:       Sven Radej <a9509961 () unet ! univie ! ac ! at>
Date:       1997-07-15 9:58:23
[Download RAW message or body]

Hi, Bernd,

On 14-Jul-97 Bernd Johannes Wuebben wrote:
>
>
>On 14-Jul-97 Sven Radej wrote:
>>kedit:  Floats&Resizes ok.
>>
>>kfax:   Floats&Resizes fine.
>
>Sven, what's the difference between fine and ok. What problems remain
>fro apps such as kedit and kfax?

#define ok fine

No problems with kedit and kfax. Both apps run fine (i.e ok). The
problems with some apps (karm, kjots, kdehelp) is that they get
ABORT  when they are quitted via menu item Quit or Exit  or
WM-button while their toolbar is still floating. Kedit and Kfax don't
have such problems.

If you open more Kedit windows, and close them with WM toolbars remain
floating: here's a patch for it:

--- kedit.0.cpp Tue Jul 15 10:04:09 1997
+++ kedit.cpp   Tue Jul 15 10:07:24 1997
@@ -101,12 +101,13 @@
 TopLevel::~TopLevel (){
 
   delete file;
   delete edit;
   delete help;
   delete options;
+  delete toolbar;
 }
----END--- 
 
Such thing should be done with kfm, too. Apps that get ABORT (and
core dump, probably) are those who delete application instance on
their exit (karm); kdehelp has some signal catching on its exit, and
kjots gets ABORT although it doesnt delete application instance. Maybe
it has something to do with Kaplication destructor, I noticed few
messages "No main widget while running destructor". I'm not shure about
that. Anyway, everything works fine if you embed toolbar back before
exiting. If somebody cannot get his app to exit cleanly, let me know.

The message I get with problematic apps is this:

ASSERT: "it.count() == 0" in qwidget.cpp (662)
X Error: BadWindow (invalid Window parameter)
  Major opcode:  1
IOT trap/Abort

?
Bye,
--                               
Sven

[prev in list] [next in list] [prev in thread] [next in thread]