Hi
It seems on MacRuby 0.8 that a subclass of NSWindowController has #init called,
but #initialize is not called.
It seems really odd to have two different initialize methods, and particularly
when one of them breaks away from
what is convention in Ruby. Is this intended?
Thanks
Rob
___
I use #init whenever I’m dealing with Cocoa(-like) classes and #initialize when
it's pure Ruby. I do the same with regards to camel and snake casing. Also note
that #init is not supposed to take arguments, whereas #initialize may
definitely do so.
Any classes that inherit from NSObject directly
On 24 Feb 2011, at 13:26, Eloy Durán wrote:
> I use #init whenever I’m dealing with Cocoa(-like) classes and #initialize
> when it's pure Ruby. I do the same with regards to camel and snake casing.
> Also note that #init is not supposed to take arguments, whereas #initialize
> may definitely d
Hi, I'm trying to apply a predicate to a core data fetch and hitting
EXC_BAD_ACCESS.
I've successfully used NSPredicate to filter an array's contents, but all my
attempts to use NSPredicate with Coredata fail.
I'm using framework 'Coredata' and framework 'Foundation' and this is the
method th
Greetings,
What's the output up to the crash point?
I didn't realize you could do Pointer.new(:id), I'm still using
Pointer.new_from_type('@'). :)
Check entityDescription for nil, also. If for some reason it can't resolve
your entity it'll return nil, and that might blow up in a way like you're
Hi Zak,
I'm running MacRuby revision 5236 with BridgeSupport Preview 3 and the
following script works fine:
framework 'AudioToolbox'
url = NSURL.fileURLWithPath "/test/loops/Lounge Vibes 01.caf"
audioFileID_ptr = Pointer.new_with_type '^{OpaqueAudioFileID}'
p Aud
On Tue, Feb 22, 2011 at 8:31 PM, Laurent Sansonetti
wrote:
> Hi,
> As of r5239 in trunk, the default build process will no longer build for
> both i386 and x86_64, but just x86_64. This is an attempt at accelerating
> the build process and reducing the framework objects size.
> We are however not
On Wed, Feb 23, 2011 at 6:51 PM, Laurent Sansonetti
wrote:
> Are you using the new macruby_deploy --gem option to embed the gems?
>
I'm not ... I'm using macruby_deploy --embed to embed MacRuby, and then my
own custom Rake task to 1) copy the gem files into the application; 2) run
install_name_to
