CoreData 绑定不保留一个实体属性
我有一个简单的表单，上面有 3 个文本框和一个弹出按钮。这些字段绑定到 coredata 实体（Account），并与第二个实体（AccountType）有一种关系。弹出按钮列表由 AccountType 实体填充，并绑定到 Account.type 关系。我还有一个保存按钮，用于从表单控制器代码执行当前实体的保存...
NSError *error;
if (![[self managedObjectContext] save: &error]) {
NSLog(@"Unresolved error %@, %@", error, [error userInfo]);
}
除了我的一个文本框（称为 textbox3）的内容之外，所有内容都很好地保留在我的 xml 后备存储中。 textbox1、textbox2 和关系很好地保存到 XML 文件中，但 textbox3 没有任何内容，保存时也没有任何错误。
如果我删除 textbox3，除了 textbox2 之外，所有内容都会保存得很好。如果我将 textbox3 复制到表单上，则同一实体属性（textbox1、textbox2、textbox3）有 2 个绑定，并且关系保持得很好。
有人以前用 coredata 见过这种行为吗？
非常感谢任何帮助。
I have a simple form with 3 text boxes and one popup button on it. These fields are bound to a coredata entity (Account) with one relationship to a second entity (AccountType). The popup button list is populated from the AccountType entity and is bound to the Account.type relationship. I also have a save button which performs a save of the current entity from the forms controller code...
NSError *error;
if (![[self managedObjectContext] save: &error]) {
NSLog(@"Unresolved error %@, %@", error, [error userInfo]);
}
Everything persists to my xml backing store just fine except for the contents of one of my text boxes, call it textbox3. textbox1, textbox2 and the relationship save just fine to the XML file, but nothing for textbox3, nor are there any errors on the save.
If I remove textbox3, everything saves just fine except textbox2. If I instead copy textbox3 onto the form so there are 2 bindings for the same entity attribute, textbox1, textbox2, textbox3 and the relationship persist just fine.
Has anyone seen this behavior before with coredata?
Any help is much appreciated.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
有多种方法可以实现此目的，具体取决于应用程序的设计。 AppKit UI 元素实现了
NSEditor，因此您可以使用-commitEditing。我还看到人们改变firstResponder来强制字段编辑器提交，尽管我认为这是一种黑客行为。There are a number of ways to do this, depending on the design of your app. The AppKit UI elements implement
NSEditorso you can use-commitEditing. I've also seen people shift thefirstResponderto force the field editor to commit, although I would consider this a hack.