I realize that this question is very vague, but I'm just baffled but it.
I have an NSLevelIndicator with its value bound to my model's myEntity.Selection.Priority attribute. Priority is a required Float with a min value of 0, max of 3, and default of 1. How it functions is that I have a table view, and I want to select an item in a table view and modify its priority. The problem is that if I select an item, modify the priority through the level indicator, go to another item, and then click back to the original item, the level indicator has gone back to its default value.
I had no idea, so I created an attribute called myPriority and made it exactly the same as priority. I then bound the level indicator's value to my model's myEntity.Selection.myPriority attribute. Except this time it works. So I do a project find to find any files that mention priority, and I hit on a file. The level indicator also has an IBAction and an IBOutlet, both of which are links to this file. So I thought, it must be this, except all the code in that files is commented out. Right now, all that should be happening is the simplest behavior of setting the priority, and yet it works with one and doesn't work with another. Does anyone have any ideas of further places to look?
Thanks, - Walker Argendeli _______________________________________________ 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
