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

List:       kde-core-devel
Subject:    Re: KAction and statusText
From:       Holger Freyther <freyther () gmx ! net>
Date:       2001-12-29 13:39:09
[Download RAW message or body]

Am Samstag, 29. Dezember 2001 06:41 schrieb Ellis Whitehead:
> Hi Holger,
>
> > IIRC we decided it should stay. It was on core-devel allready
>
> Hmm... I committed the removal after reading David's message but before
> reading yours.  I did a search on "statusText" in kde-core-devel, and
> nothing but this thread came up.  Do you recall if the discussion was on
> something related that I could look up?
Hi Ellis, all,
it doesn't matter anyhow. Actually I'm glad you removed it. 
http://lists.kde.org/?l=kde-core-devel&m=100589064631354&w=2
was the link. I thought when the function was voted to stay the property 
should stay too

regards Holger 
>
> Ciao,
> Ellis
>
> On Friday 28 December 2001 06:38 pm, Holger Freyther wrote:
> > Am Freitag, 28. Dezember 2001 18:38 schrieb David Faure:
> > > On Friday 28 December 2001 15:06, Ellis Whitehead wrote:
> > > > The statusText functions in KAction are now depricated.  Do we
> > > > still want to leave the following?
> > > >
> > > >   Q_PROPERTY( QString statusText READ statusText WRITE setStatusText
> > > > )
> > > >
> > > > If yes, should we put it in a #ifndef KDE_NO_COMPAT block?
> > >
> > > moc isn't going to notice the KDE_NO_COMPAT ifdef.
> > > Better remove the property altogether imho, if the method is
> > > deprecated.
> >
> > Hi,
> > IIRC we decided it should stay. It was on core-devel allready
> >
> > regards Holger
[prev in list] [next in list] [prev in thread] [next in thread]