blocks|key|2311650|text|如果要显示的内容不会改变，可以跳过为该小部件创建属性或IBOutlet。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2311651|例如，在一个屏幕中，您有一个标签和一个textfield，标签总是具有字符串"Name:“，而textfield用于从用户获取输入，您必须为textfield创建一个引用出口，以访问来自用户的数据输入。在这里创建一个标签引用出口没有任何意义。|2311652|我希望你明白重点。|2311653|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

If what you are going to display is not going to change, you can skip creating a property or a IBOutlet for that widget.

For example in a screen where you have a label and a textfield and the label always has the string "Name:" and textfield is used for getting input from the user, you have to just create a referencing outlet for the textfield to access the data input from the user. Creating a referencing outlet for label doesn't make any sense here. 

I hope you get the point.

blocks|key|640921|text|没有必要为每个IBOutlet创建一个属性。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|640922|具体来说，如果您只从声明它的类访问出口，则严格地不需要该属性。如果您有一个属性，您将得到属性所提供的优势，但您始终可以直接引用该出口。|640923|如果计划从另一个类访问出口，则属性非常有用，因此不必定义自己的setter和getter方法。|640924|entityMap^0|7|8|0|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@]|D|@]|E|$]]|$1|H|3|I|5|6|7|P|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|Q|8|@]|D|@]|E|$]]]|K|$]]

It is not necessary to create a property for each <code>IBOutlet</code>.

Specifically, if you access the outlet only from the class where it is declared, you do not strictly need the property. If you have a property, you get the advantages that properties offer, but you could always directly refer the outlet directly.

If you plan to access the outlet from another class, then a property is useful so you don't have to define yourself setter and getter methods.

blocks|key|640928|text|如果您只想对创建XIB的视图使用IBOutlet，那么就不需要在这里设置属性。但是，是的，每次我们为视图创建IBOutlet时使用它是很好的实践，但不是强制性的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|640929|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you want to use the IBOutlet for only the view for which you created the XIB then no need to set the property here. But yes, it is good practice to use but not mandatory to use everytime we create IBOutlet for the view.

blocks|key|639145|text|属性是Objective中的一个特性，它允许我们自动生成访问器，也有一些其他的好处。因此，正如Praveen给您举了一个使用Label和UIText的例子，我只是很少探索。假设您与UILabel无关，您不完全需要设置属性，但是如果用户要求给您的UITextField提供一些文本，则必须设置属性。如果将属性设置为retain，则必须在viewDidUnload中释放它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|639146|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Properties are a feature in Objective-C that allow us to automatically generate accessors, and also have some other side benefits. so as Praveen S gave you an example with Label and UIText i just little explore.
Lets say you have nothing to do with UILabel you do not exactly need to set the properites but if are asking from user to give some text to your UITextField you have to set the properties. and if you setting the properties with retain, you must release it in viewDidUnload.

blocks|key|2311867|text|我喜欢从便于内存管理和外部访问的角度来看待它。如果您需要从外部访问它，显然要创建一个属性。(是的，轻松的内存管理，如果很容易，你不会搞砸它，如果你不把它搞砸了，它以后不会变成一个bug+)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2311868|80%25的时间，我的视图控制器有IBOutlets，没有其他人访问他们，因此象牙工作。问题是，当您不使用@property时，赋值仍然保留。然后你需要记得发布它，即使你自己没有保留它，这是我发现的违反直觉的。|2311869|由于这个原因，我通常使用@property+(赋值)来表示我不会更改的属性，而@property+(retain)则用于其他所有内容，并且不会直接将IBOutlets声明为ivars。|2311870|示例：|2311871|@interface+something+:+NSObject+{
++++//This+one+needs+to+be+RELEASED+then+set+to+nil+in+both+viewDidUnload,+and+dealloc.
++++IBOutlet+UILabel+*+myLabel;
++++//also+cannot+be+accessed+outside+of+"something"+class+(technically+it+can,+but+don't+do+that)
++++//I+NEVER+declare+my+outlets+this+way.
}

//This+one+can+just+be+set+to+nil+in+viewDidUnload+and+dealloc
@property+(nonatomic,+retain)+UILabel+*+myOtherLabel;
//it+can+also+be+accessed+from+mySomething.myOtherLabel+by+any+other+class.

//This+one+just+works.+I+don't+own+it,+the+view+owns+it,+so+I+don't+retain/release.
@property+(nonatomic,+assign)+UILabel+*+myOtherOtherLabel;
//It+also+provides+access+to+outsiders.
//I+wouldn't+recommend+using+this+type+if+you+want+to+change+the+value+though.|code-block|syntax|javascript|2311872|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|R|8|@]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

I like to look at it is in terms of ease of memory management, and external access. If you need to access it externally, obviously make a property. (Yes ease of memory management, if it's easy you won't mess it up, if you don't mess it up it doesn't become a bug later)

80% of the time my view controller has the IBOutlets and nobody else accesses them, therefore ivars work.
The problem is that when you don't use @property, the assigned value is still retained. Then you need to remember to release it even though you didn't retain it yourself, which I found counter-intuitive.

For that reason I usually use @property (assign) for the ones I won't be changing, and @property (retain) for everything else, and never declare IBOutlets directly as ivars.

Example:

<pre><code>@interface something : NSObject {
 //This one needs to be RELEASED then set to nil in both viewDidUnload, and dealloc.
 IBOutlet UILabel * myLabel;
 //also cannot be accessed outside of "something" class (technically it can, but don't do that)
 //I NEVER declare my outlets this way.
}

//This one can just be set to nil in viewDidUnload and dealloc
@property (nonatomic, retain) UILabel * myOtherLabel;
//it can also be accessed from mySomething.myOtherLabel by any other class.

//This one just works. I don't own it, the view owns it, so I don't retain/release.
@property (nonatomic, assign) UILabel * myOtherOtherLabel;
//It also provides access to outsiders.
//I wouldn't recommend using this type if you want to change the value though.
</code></pre>

blocks|key|639192|text|如果您想要更改显示的内容，那么您应该添加一个property..for示例，如果我们想要更改标签文本，那么我们需要使用IBOutlet+nd属性，以便我们能够到达框架将从我们的nib构建的label控件。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|639193|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you want to change the Contents of your display then you should add the property..for an example if we want to change the label text then we need to use IBOutlet nd Property so that we need to able to get to the label control that the framework will build from our nib..

We create property for a variable for using it in some other view. Same we do for IBOutlets. But not always for using them. Is it necessary to create property for each IBOutlet we just created it our xib? Or is it only a good practice to do so?

Should every IBOutlet have a property?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我们为变量创建属性，以便在其他视图中使用它。我们对IBOutlets也是这样。但不一定是为了利用它们。是否需要为我们刚刚创建的每个IBOutlet创建xib属性？抑或这只是一种良好的做法？

问每个IBOutlet都应该有一个属性吗？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问每个IBOutlet都应该有一个属性吗？EN