On Jul 7, 2011, at 2:43 AM, Manfred Schwind wrote:
>> On Mac OS X, all top-level objects get an -awakeFromNib.
>> On iOS, top-level objects do not get -awakeFromNib.
>
> Uh? This was news to me and I immediately tested this.
> My tests show:
>
> - On OS X all objects of the nib including the fi
it's documented in "The NIB Object Life Cycle", a page you should have
bookmarked!!
It sends an awakeFromNib message to the appropriate objects in the nib file
that define the matching selector:
In Mac OS X, this message is sent to any interface objects that define the
method. It is also sent t
Le 7 juil. 2011 à 11:43, Manfred Schwind a écrit :
> - On OS X all objects of the nib including the file's owner get an
> awakeFromNib.
> - On iOS also all objects of the nib (including top-level objects!) but NOT
> the file's owner get an awakeFromNib.
>
> BTW, I can't find this documented so
> On Mac OS X, all top-level objects get an -awakeFromNib.
> On iOS, top-level objects do not get -awakeFromNib.
Uh? This was news to me and I immediately tested this.
My tests show:
- On OS X all objects of the nib including the file's owner get an awakeFromNib.
- On iOS also all objects of the
Le 6 juil. 2011 à 18:10, Douglas Davidson a écrit :
> It isn't necessary to use @"." here; you should be able to pass nil for that
> argument if the resources in question are not in a subdirectory. From the
> header comments: "subpath is a relative path to a subdirectory inside the
> relevant
On Jul 6, 2011, at 5:27 AM, Alexander Reichstadt wrote:
> NSArray *sometest = [[NSBundle mainBundle] pathsForResourcesOfType:@"nib"
> inDirectory:@"."];
It isn't necessary to use @"." here; you should be able to pass nil for that
argument if the resources in question are not in a subdirectory.
Le 6 juil. 2011 à 17:09, Kyle Sluder a écrit :
> On Wed, Jul 6, 2011 at 7:08 AM, Vincent Habchi wrote:
>> However, I end up in a cycle, whereby the call to [NSBundle
>> loadNibNamed:name owner:self] generates a (unexpected) callback to
>> -awakeFromNib. How come? Is this normal behavior?
>
> T
On Wed, Jul 6, 2011 at 7:08 AM, Vincent Habchi wrote:
> However, I end up in a cycle, whereby the call to [NSBundle loadNibNamed:name
> owner:self] generates a (unexpected) callback to -awakeFromNib. How come? Is
> this normal behavior?
This is normal behavior on Mac OS X. It is not normal beha
On Jul 6, 2011, at 9:08 AM, Vincent Habchi wrote:
> implementing Alexander's idea, I wrote this code to load Nibs ending with
> "Connector":
>
> - (void)fetchAndInitializeConnectors {
> // Search all NIB files ending with "connector" and load them
> for (NSString * path in [[NSBundle
Re-hi,
implementing Alexander's idea, I wrote this code to load Nibs ending with
"Connector":
- (void)fetchAndInitializeConnectors {
// Search all NIB files ending with "connector" and load them
for (NSString * path in [[NSBundle mainBundle]
pathsForResourcesOfType:@"nib" inDire
Le 6 juil. 2011 à 14:27, Alexander Reichstadt a écrit :
> Try:
> NSArray *sometest = [[NSBundle mainBundle] pathsForResourcesOfType:@"nib"
> inDirectory:@"."];
> for (id thisOne in sometest){
> NSLog(@"This is a path:%@",thisOne);
> }
Thanks for the hint, I'll do that right away.
Viel Da
Try:
NSArray *sometest = [[NSBundle mainBundle] pathsForResourcesOfType:@"nib"
inDirectory:@"."];
for (id thisOne in sometest){
NSLog(@"This is a path:%@",thisOne);
}
Am 06.07.2011 um 14:04 schrieb Vincent Habchi:
> Hi there,
>
> I'm, as we say in French, tearing my hair away with this
Hi there,
I'm, as we say in French, tearing my hair away with this little problem:
Briefly, I have an object in a NIB file, and I'd like it to load further NIB
files (through +[NSBundle loadNibNamed:owner:] calls), all of them ending with
the same suffix (ex: onefoo, twofoo, threefoo).
I just
13 matches
Mail list logo