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

List:       kde-core-devel
Subject:    Re: KAction and KAccel
From:       weis <weis () stud ! uni-frankfurt ! de>
Date:       1999-12-01 12:23:52
[Download RAW message or body]

Hi,

On Wed, 1 Dec 1999, Waldo Bastian wrote:

> On Tue, 30 Nov 1999, David Faure wrote:
> > On Tue, Nov 30, 1999 at 06:20:05PM +0100, Waldo Bastian wrote:
> > > On Tue, 30 Nov 1999, Richard Moore wrote:
> > > > Waldo Bastian wrote:
> > > > > 
> > > > > > Sirtaj Singh Kang wrote:
> > > > > > > On Tue, Nov 30, 1999 at 08:05:29AM -0700, Kurt Granroth wrote:
> > > > > > > > I'm investigating the possibility of hacking some code to let KAccel
> > > > > > > > and KAction "know" about each other.. but I would have to convert
> > > > > > > > KAccel to a QObject (and add a signal) and add quite a few new
> > > > > > >
> > > > > > > This seems like the wrong approach to me. A KAccel should simply be a special
> > > > > > > case of an action, ie is not connected to any visual interface elements.
> > > > > > > Are there any differences that I've missed?
> > > > > 
> > > > > Yes. The accel should shown up in the menu. So the KAction should have
> > > > > some knowledge about KAccels to be able to provide a menu-option with
> > > > > the desired information.
> > > > 
> > > > Wouldn't that happen anyway when the Kaction was added to the menu? I
> > > > don't see how this changes anything.
> > > 
> > > I have no idea. The KAction class does not have any documentation.
> > > 
> > It is only a reimplementation of the QAction class - the API is unchanged.
> > You can look at the QAction documentation instead.
> 
> Where can I find that? My qaction.h does not have any documnetation.

I would be happy if it had docu :-) Then I would not need to write
some (or force Matthias to do so :-)

Bye
Torben

> Cheers,
> Waldo
> 
> 

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