[Rubycocoa-devel 512] Re: apple-unstable: QTKit

Back to archive index

Eloy Duran eloy.****@gmail*****
Tue Dec 19 20:30:22 JST 2006


Just to clarify my point a bit more, because my previous email
was written way past bed time :)

I think part of the problem lies in the descriptor (oc_type or
whatever it's called) of the
returned struct.

If we take a look at bridge-support/Foundation.xml for example:
NSPoint encoding: {_NSPoint="x"f"y"f}

Now I remember that, once when I was hacking away at the ocdata_conv part
of the old skool rubycocoa, a NSPoint structure actually starts with a
string like:
{_NSPoint.......} which is of course how you can identify this.

But a QTTime & QTTimeRange structure for some reason don't have this
nice description, like I said in the previous email, they return:
QTTime encoding: {?=qll}
QTTimeRange encoding: {?={?=qll}{?=qll}}

So my guess is that you parsed the description, of the vars inside the struct,
from the QTKit headers no? This is of course good to have the method
names that should be used to set/get the vars, BUT it seems that this
is not a waterproof solution to do the conversion over the bridge.....

Well I hope that makes my point a bit clearer.

Cheers,
Eloy.


On 12/19/06, Laurent Sansonetti <lsans****@apple*****> wrote:
> Thanks a lot for the nice feedback Eloy, I'm going to check this out
> later today if possible.
>
> Laurent



More information about the Rubycocoa-devel mailing list
Back to archive index