You are very welcome :-).

I know it can be tricky, because one would tend to believe the bridgesupport 
files are all correct, but there is definitely a lot of area for improvement 
(which is being worked on ;-))

Can I close the bug, if everything is working?

P.S.: My first name is actiually Thibault :P

-- 
Thibault Martin-Lagardette



On Jun 15, 2010, at 08:10, Ed wrote:

> Thanks Martin, that explains it.
> 
> Ed
> 
> On Jun 14, 2010, at 7:07 PM, MacRuby wrote:
> 
>> #376: The second 'pointer' of a double pointer type is ignored
>> ---------------------------------+------------------------------------------
>> Reporter:  m...@…               |       Owner:  lsansone...@…        
>>    Type:  defect               |      Status:  new                  
>> Priority:  blocker              |   Milestone:                       
>> Component:  MacRuby              |    Keywords:                       
>> ---------------------------------+------------------------------------------
>> 
>> Comment(by martinlagarde...@…):
>> 
>> What you can add in `MusicPlayer.bridgesupport` is information about music
>> player being an opaque struct. Between structs and enums, I added the
>> following line:
>> {{{
>> #!xml
>> <opaque name='OpaqueMusicPlayerRef' type='^{OpaqueMusicPlayer}'/>
>> }}}
>> 
>> Then when I run the script:
>> {{{
>> $> macruby t.rb
>> ^{OpaqueMusicPlayer}
>> $>
>> }}}
>> 
>> -- 
>> Ticket URL: <http://www.macruby.org/trac/ticket/376#comment:5>
>> MacRuby <http://macruby.org/>
>> 
>> _______________________________________________
>> MacRuby-devel mailing list
>> MacRuby-devel@lists.macosforge.org
>> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
> 
> _______________________________________________
> MacRuby-devel mailing list
> MacRuby-devel@lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

_______________________________________________
MacRuby-devel mailing list
MacRuby-devel@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel

Reply via email to