This is a discussion on Re: [KDE4] QCString -> DCOPCString - KDE ; On Sunday 07 August 2005 10:04 am, Stephan Kulow wrote: > Am Samstag 06 August 2005 04:36 schrieb Gary Cramblitt: > > The KSpeech DCOP interface in KDE 3 has a number of arguments of type > > QCString. It ...
On Sunday 07 August 2005 10:04 am, Stephan Kulow wrote:
> Am Samstag 06 August 2005 04:36 schrieb Gary Cramblitt:
> > The KSpeech DCOP interface in KDE 3 has a number of arguments of type
> > QCString. It appears that these should be changed in KDE4 to DCOPCStri=
> > (which inherits from QByteArray)? I assume this will break all apps th=
> > use KSpeech? If so, would QByteArray be a better choice? What are oth=
> > DCOP interfaces doing about this issue?
> DCOPCString is exactly what replaces QCString - QCString is no more and
> used to inherit QByteArray before just as now is DCOPCString.
Looking around in kdelibs, I'm finding a variety of answers.
* Sets m_dcopName basically to @p dcopName,
* and then registers with DCOP.
* @param dcopName name to set the DCOP name to
* @param rootMode true if the kcmshell is embedding
void setDCOPName(const Q3CString &dcopName, bool rootMode );
class KIMProxyIface : virtual public DCOPObject
virtual void contactPresenceChanged( QString uid, DCOPCString appId, int =
presence ) =3D 0;
* Indicates that a contact's presence has changed
* @param uid the KABC uid whose presence changed.
* @param appId the dcop application id of the program the signal originat=
* @param presence the new numeric presence @ref presenceStatus
void contactPresenceChanged( QString uid, Q3CString appId, int presence );
There seem to be 3 choices for DCOP single-byte character strings:
Functionally, all 3 are essentially the same. However, since the compiler =
picky about typing, I think we should agree on a "standard". Should =
DCOPCString be that standard?
Gary Cramblitt (aka PhantomsDad)
KDE Text-to-Speech Maintainer
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscrib=