rubycocoa-talk

[Rubycocoa-talk] Building NSMatrix from scratch.

[Dave H. <gr...@gr...>]

OK, building my cells from scratch isn't working either.

		matrixFrame = NSRect.new
		matrixFrame.size.height = 40.0
		matrixFrame.size.width = 28.0
		matrixFrame.origin.x = 20.0
		matrixFrame.origin.y = 20.0
		newMatrix = OSX::NSMatrix.alloc.initWithFrame(matrixFrame)

What the log says is

	NSMatrix(0x5c0cc60) - NSView not correctly initialized. Did you forget 
to call super?

I don't understand the question. Does it not like my NSRect? The 
program keeps running, but the matrix doesn't appear in the window.

Re: [Rubycocoa-talk] Building NSMatrix from scratch.

[kimura wataru<ki...@us...>]

Hi,

OSX::NSRect#new generates a NSRect object.

  OSX::NSRect.new(origin_x, origin_y, size_widhth, size_height)


Mon, Jan 2, 2006 4:45:48 PM, Dave Howell wrote:
>OK, building my cells from scratch isn't working either.
>
>		matrixFrame = NSRect.new
>		matrixFrame.size.height = 40.0
>		matrixFrame.size.width = 28.0
>		matrixFrame.origin.x = 20.0
>		matrixFrame.origin.y = 20.0
>		newMatrix = OSX::NSMatrix.alloc.initWithFrame(matrixFrame)
>
>What the log says is
>
>	NSMatrix(0x5c0cc60) - NSView not correctly initialized. Did you forget 
>to call super?
>
>I don't understand the question. Does it not like my NSRect? The 
>program keeps running, but the matrix doesn't appear in the window.
>

This message is a warning not an error. The view is initialized correctly
and you can ignore the message. When RubyCocoa generantes a instance of 
subclass of NSView, this message is displayed.

I think that is a bug of RubyCocoa but to solve this problem is difficult.


-- 
kimura wataru

Re: [Rubycocoa-talk] Building NSMatrix from scratch.

[Dave H. <gr...@gr...>]

On Jan 5, 2006, at 7:03, kimura wataru wrote:

>>
>> 	NSMatrix(0x5c0cc60) - NSView not correctly initialized. Did you 
>> forget
>> to call super?
>>
>> I don't understand the question. Does it not like my NSRect? The
>> program keeps running, but the matrix doesn't appear in the window.
>>
>
> This message is a warning not an error. The view is initialized 
> correctly
> and you can ignore the message. When RubyCocoa generantes a instance of
> subclass of NSView, this message is displayed.
>
> I think that is a bug of RubyCocoa but to solve this problem is 
> difficult.
>
Aha.

So if I'm making this new NSView object, how does Cocoa know in which 
window (or rather, which contentView of which window) I want this new 
NSMatrix to appear? That's my first guess as to why I can't see it: I 
haven't "put it into the window" yet.

(My Cocoa Programming book doesn't seem to think anybody would ever 
want to create these things programmatically.)

Re: [Rubycocoa-talk] Building NSMatrix from scratch.

[Dave H. <gr...@gr...>]

On Jan 5, 2006, at 18:51, Dave Howell wrote:

> Aha.
>
> So if I'm making this new NSView object, how does Cocoa know in which 
> window (or rather, which contentView of which window) I want this new 
> NSMatrix to appear? That's my first guess as to why I can't see it: I 
> haven't "put it into the window" yet.
>
> (My Cocoa Programming book doesn't seem to think anybody would ever 
> want to create these things programmatically.)
>

Never mind. I found it.

inside my NSWindowController object...


self.window.contentView.addSubview(MyMatrix.alloc.init(parameters))

Re: [Rubycocoa-talk] Building NSMatrix from scratch.[MESSAGE NOT SCANNED]

[Jonathan P. <jp...@dc...>]

On 3 Jan 2006, at 0:45, Dave Howell wrote:

> What the log says is
>
> 	NSMatrix(0x5c0cc60) - NSView not correctly initialized. Did you  
> forget to call super?
>
> I don't understand the question. Does it not like my NSRect? The  
> program keeps running, but the matrix doesn't appear in the window.

This log message is independent of the other problems you were  
seeing. It's a result of a peculiarity in the way RubyCocoa  
initialises objects, whereby the call sequence actually looks like:

   [[[NSViewSubClass alloc] retain] init]

The implementation of 'retain' for NSView notices that init hasn't  
been called yet and issues that log message. This can probably be  
fixed in RubyCocoa. For now, don't worry about it.

[The above is from my memory of investigating this a bit a month or  
so back - some of the details may be slightly different]