Ah, also nsICancelable seems to not be a frozen interface. So, you
might think twice about including it in your object's inheritance
chain anyway.
John.
John Bandhauer wrote:
It's fine if you are ready to move on. But, if you didn't already
confirm that your C++ QueryInterface implementation handles the
nsICancelable case then I suggest you take a moment to do so. An
improperly implemented C++ xpcom object might bite you again later.
John.
[EMAIL PROTECTED] wrote:
Well, the no-parms approach got results. Looks like there were
problems passing my C++ object into the js object. Don't know why, not
going to spend any time figuring it out.
Instead of passing XPCOM objects, I'll just use a cookie technique.
Thanks to all.
________________________________
From: [EMAIL PROTECTED] on behalf of John
Bandhauer
Sent: Tue 12/5/2006 1:36 PM
To: [email protected]
Subject: Re: XPCOM cpp to js callback
I'm short on ideas. Perhaps if you make a more complete version of
your code available then someone will see something. For instance, I
don't see the QueryInterface implementation of your C++ object. If
that method fails to handle the nsICancelable case then XPConnect will
fail to build a wrapper around it when it is passed to the JS code -
and the call would fail. There are other such possibilities :)
You could also just try adding a method with no params to the callback
interface, implement it in JS, and try calling that. i.e. get
*something* working and then figure out what is different about what
doesn't work.
John.
_______________________________________________
dev-tech-xpcom mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-xpcom
_______________________________________________
dev-tech-xpcom mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-xpcom
