From koffice Tue Jun 29 20:28:12 1999 From: Simon Hausmann Date: Tue, 29 Jun 1999 20:28:12 +0000 To: koffice Subject: Re: bug in kscript? X-MARC-Message: https://marc.info/?l=koffice&m=93068769926699 On Tue, 29 Jun 1999 weis@stud.uni-frankfurt.de wrote: > Hi, > > On Sat, 26 Jun 1999, Simon Hausmann wrote: > > > Hi, > > > > While playing around with the CORBA support in KScript noticed a > > bug: > > When a CORBA method returns an object reference, the >>= operator with > > CORBA::Any::to_object in ksUnpack fails. > > > > So for example > > ---- snip ---- > > import KDED; > > > > main > > { > > kded = KDED.InitialReferences( ior_of_kded_returned_by_a_builtin_func ); > > naming = kded.knamingService(); > > } > > ---- snip ---- > > fails in ksUnpack() in the extraction of the object reference, which > > KDED::InitialReferences::knamingService() returns. > > > > Bug in KScript or MICO? > > O la la. I tried with KSpread and unpacking worked great. > So it seems to be at least somehow complicated. I will test. > > How can I get the IOR of the kded without hacking kded or kscript ? "xprop -root KDED_RESOURCES" , then copy&paste :-) (...I know, I know, now the perl/sed hackers will come up with a much smarter solution to "extract" the IOR of this output :-) Ciao, Simon -- Simon Hausmann http://www.kde.org/