Re: NIB Files + Views. Is it a good practice?
Re: NIB Files + Views. Is it a good practice?
- Subject: Re: NIB Files + Views. Is it a good practice?
- From: Fabio Mancinelli <email@hidden>
- Date: Sun, 22 Oct 2006 23:17:45 +0200
Keary Suska wrote:
on 10/22/06 6:18 AM, email@hidden purportedly said:
Well actually I have noticed it and I use it.
Here it is a screenshot of my application:
http://img221.imageshack.us/img221/600/picture1eg8.png
What it does is very straightforward... By clicking on the buttons it
replaces the content of the CustomView with View1 or View2.
My question focused on how to create View1 and View2 instances.
What CustomView has to do with them?
If I understand you correctly, you want to "swap" out one NSView object for
another, at the click of a button? If so, this is only something that can be
done entirely in code AFAIK. You'll have to leave IB out of the picture. But
it's probably the harder way to do the job.
Well actually the code I wrote was just to experiment... I don't want to
do any swapping like that in a real world case :)
I was just playing with View instances in a NIB file and I had some
doubts on how they were actually created.
It turned out that I simply ignored that a CustomView could be dragged
from the palette directly to the NIB file :)
Thank you
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden