[prev in list] [next in list] [prev in thread] [next in thread]
List: koffice
Subject: Re: bug in kscript?
From: Simon Hausmann <tronical () gmx ! net>
Date: 1999-06-29 20:28:12
[Download RAW message or body]
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 <hausmann@kde.org>
http://www.kde.org/ <tronical@gmx.net>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic