On Feb 21, 2008, at 14:06, Ken Ferry wrote:
Hm, sorry if the docs confused you.. if you can point at the docs that
made you think this, it'd be great to have a bug.
There's:
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaViewsGuide/SubclassingNSView/chapter_6_section_2.html#/
On Thu, Feb 21, 2008 at 1:46 PM, Kyle Sluder
<[EMAIL PROTECTED]> wrote:
> On Thu, Feb 21, 2008 at 2:41 PM, Ken Ferry <[EMAIL PROTECTED]> wrote:
> > What's guaranteed is that all init methods on a class will funnel into
> > one of the designated init methods. A subclasser should always
> > ov
On Thu, Feb 21, 2008 at 2:41 PM, Ken Ferry <[EMAIL PROTECTED]> wrote:
> What's guaranteed is that all init methods on a class will funnel into
> one of the designated init methods. A subclasser should always
> override all designated initializers of the superclass (if he needs to
> do work at
On Thu, Feb 21, 2008 at 11:30 AM, Shamyl Zakariya <[EMAIL PROTECTED]> wrote:
> OK, sounds like I'm not out of the woods.
>
> Here's the trouble: I have some controls ( in my toolbar ) controlling
> a couple properties of the image view subclass. Specifically, a zoom
> factor and a tiling mode (
> I'm not sure -initWithCoder: is guaranteed to be called, and is
> certainly not the "proper" place to be performing object
> initialization after awaking from a nib.
What's guaranteed is that all init methods on a class will funnel into
one of the designated init methods. A subclasser should
Well, to finish this off, I just made some calls to initialize from
windowControllerDidLoadNib and averything's peachy, and no dependancy
on initWithCoder.
Shamyl Zakariya
- The fantabulous contrapulation of professor Horatio Huffnagel
On Feb 21, 2008, at 2:30 PM, Shamyl Zakariya w
OK, sounds like I'm not out of the woods.
Here's the trouble: I have some controls ( in my toolbar ) controlling
a couple properties of the image view subclass. Specifically, a zoom
factor and a tiling mode ( this is just a quick-dirty app for viewing
compressed DDS textures. I've already w
Wonderful! Now I have sane defaults and my controls bound to them have
the correct values.
Thanks for your help.
[EMAIL PROTECTED]
"finite=alright"
--David Byrne
On Feb 21, 2008, at 2:06 PM, Mike Abdullah wrote:
If the view's being loaded from a nib it's archived, so you need -
That makes sense, thank you.
[EMAIL PROTECTED]
"Such a theory has to be bizarre and elaborate, as well as being
stupid"
-- Jim Loy, regarding a hollow earth
On Feb 21, 2008, at 2:00 PM, Kyle Sluder wrote:
On Thu, Feb 21, 2008 at 1:36 PM, Shamyl Zakariya
<[EMAIL PROTECTED]> wro
On Thu, Feb 21, 2008 at 2:06 PM, Mike Abdullah
<[EMAIL PROTECTED]> wrote:
> If the view's being loaded from a nib it's archived, so you need -
> initWithCoder:
I'm not sure -initWithCoder: is guaranteed to be called, and is
certainly not the "proper" place to be performing object
initialization a
If the view's being loaded from a nib it's archived, so you need -
initWithCoder:
Mike.
On 21 Feb 2008, at 18:36, Shamyl Zakariya wrote:
I've written a subclass of NSImageView, and my intent was to set
some sane default values for some member vars in my initWithFrame:
( NSRect ) method.
H
On Thu, Feb 21, 2008 at 1:36 PM, Shamyl Zakariya <[EMAIL PROTECTED]> wrote:
> Anybody know why it wouldn't be called? It doesn't appear to be
> misspelled.
Re-read the documentation here:
http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaViewsGuide/SubclassingNSView/chapter_6_sectio
12 matches
Mail list logo
