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

List:       kde-core-devel
Subject:    KXMLGUIClient
From:       Ellis Whitehead <kde () ellisw ! net>
Date:       2002-01-01 23:16:24
[Download RAW message or body]

Hi guys,

I believe I've figured out an elegant solution to the KAccel problems I've 
been having with KAction -- but it would require that KXMLGUIClient know 
which QWidget* it's a part of, so that it can pass that pointer to "new 
KActionCollection()", so that actions created on that collection are not all 
placed in one single monolithic top-level-window KAccel object full of key 
conflicts.

The easiest way to do this would be to pass a pointer to it upon 
construction.  Problem is that it would require something like the following:

-  KXMLGUIClient();
-  KXMLGUIClient( KXMLGUIClient *parent );
+ KXMLGUIClient( QWidget *widget, KXMLGUIClient *parent = 0 );

This would, of course, break compilation on any classes which inherit from 
KXMLGUIClient.  Since the object which virtually inherits is 
probably a QWidget child as well, it might be necessary to leave off the "= 
0".

There are only a few KXMLGUIClient children in kdelibs/kdebase, so it would 
only require changing a few lines.  Can anyone who's familiar with 
KXMLGUIClient say how it's used outside of cvs?  If it's not, may I change it 
as outlined above?

Cheers,
Ellis
[prev in list] [next in list] [prev in thread] [next in thread]