disableAutoDcopRegistration() in D-BUS?

Howdy,

Is there an equivalent to
KApplication::disableDcopRegistration() for the D-BUS port?
Else you need to run the dbus-daemon 0.62 in order to run
kxml_compiler in the kdepim build process.

-- 
Let's Keep the Political Talk Out of KDE PLEASE
 
>> Visit 
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<

Allen Winter wrote:
>Howdy,
>
>Is there an equivalent to
KApplication::disableDcopRegistration() for
> the D-BUS port? Else you need to run the dbus-daemon
0.62 in order to
> run kxml_compiler in the kdepim build process.

There's no equivalent. In order to not connect to D-BUS,
you must not use 
KApplication.

-- 
Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT)
kde.org
  thiago.macieira (AT) trolltech.com     Trolltech ASA
    GPG: 0x6EF45358                   |  Sandakerveien 116,
    E067 918B B660 DBD1 105C          |  NO-0402
    966C 33F5 F005 6EF4 5358          |  Oslo, Norway
 
>> Visit 
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<

On Thu, Jun 15, 2006 at 02:10:51AM +0200, Thiago Macieira
wrote:
> Allen Winter wrote:
> >Is there an equivalent to
KApplication::disableDcopRegistration() for
> > the D-BUS port? Else you need to run the
dbus-daemon 0.62 in order to
> > run kxml_compiler in the kdepim build process.
> 
> There's no equivalent. In order to not connect to
D-BUS, you must not use 
> KApplication.
> 
is this by design (reasons?) or just not yet implemented?

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature,
please!
--
Chaos, panic, and disorder - my work here is done.
 
>> Visit 
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<

Oswald Buddenhagen wrote:
>On Thu, Jun 15, 2006 at 02:10:51AM +0200, Thiago
Macieira wrote:
>> Allen Winter wrote:
>> >Is there an equivalent to
KApplication::disableDcopRegistration() for
>> > the D-BUS port? Else you need to run the
dbus-daemon 0.62 in order
>> > to run kxml_compiler in the kdepim build
process.
>>
>> There's no equivalent. In order to not connect to
D-BUS, you must not
>> use KApplication.
>
>is this by design (reasons?) or just not yet
implemented?

Right now, just not implemented.

When porting KDE applications, we simply comment out the 
disableDcopRegistration code because, in the future, we may
want to have 
a function for that.

The problem is that QDBus::sessionBus() is a
connect-on-first-use 
function, so there's no way you can make it not connect.
What you can do 
is make KApplication not complain that it is not connected
and ignore the 
error.

I have tried to make the functions work and return valid
pointers even if 
it's not connected, but you have to be extra careful.

Finally, we decided that KApplication is going to be in
kdeui and is going 
to be used for GUI applications only. If you're writing a
non-GUI 
application, you can use QCoreApplication and initialise any
KDE 
subsystems that you may require yourself. So, even though we
may add an 
equivalent for disableDcopRegistration(), kxml_compiler has
to be ported 
to not use KApplication anyways.

-- 
Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT)
kde.org
  thiago.macieira (AT) trolltech.com     Trolltech ASA
    GPG: 0x6EF45358                   |  Sandakerveien 116,
    E067 918B B660 DBD1 105C          |  NO-0402
    966C 33F5 F005 6EF4 5358          |  Oslo, Norway
 
>> Visit 
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<