site_archiver@lists.apple.com Delivered-To: cocoa-dev@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ieee.org; s=google; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=P8+bzIdd3OaQ0xk0bhvwdIsAPrh6+Dk/wbNxftWonek=; b=AFszxUEpHeB4HGkOw2/5toxZJOSXO92loshjpba27OixM4ZWoDsfnCX7bLME3whDJB lgKNN3rSdUTV+7FngLbOXZRxl21nUM8PEa/6hbNB+lvJ64to55IcboedUTr9kGycMBns i/pOjb+5AOv2oZwLxR+8d2T6UFb7u0R6pw0j4= On 2019 Jun 19, at 21:35, Kurt Bigler via Cocoa-dev <cocoa-dev@lists.apple.com> wrote:
I would like to be able to traverse the top-level object list in a macOS nib without instantiating the objects. But I'd like to be able to get at the attributes of each top-level item to decide whether to instantiate it, and then of course to control instantiation on an object-by-object basis based on that. Is this possible?
Using available API, you must *load* the nib file. The method loadNibNamed(_:owner:topLevelObjects:) will return an array of top level objects. If that is too much “instantiate” for you, then I think the answer to your question is “no”, unless you want to reverse-engineer the nib file format, then have your app read that file. I think the correct solution to this problem, if you are trying to reduce resource usage, is to put the views or whatever you’re trying to avoid instantiating into separate nib files, and only load the nib files you need. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl... This email sent to site_archiver@lists.apple.com