> On Aug 4, 2016, at 11:34 PM, livinginlosange...@mac.com wrote: > > I have 8 NSComboBoxes in my application organzied into 4 pairs, each pair > sharing an NSComboBox delegate. I have had some users periodically say that > the combo-boxes get confused. ComboBox A will wrongly display ComboBox B’s > data. I have scoured my code for an places where I might perform an > assignment as opposed to performing an equality comparison. I have a hard > recreating this event. More often than not, I experience my combo boxes not > working. I’ll restart and everything will be fine. Not be able to repeat the > issue is the biggest problem. > > My next step to solve this issue will be to catch the popupwillopen > notifications so I can re-set the delegate. > > Does anyone have any ideas on how to solve this issue?
There is not much anyone can help without seeing code. One would think that it either has to do with the assignment of the delegate or the assignment of the outlets/properties of the delegate, or both. Could be a memory issue, which makes more sense for crashes, but is one way objects can trade places. I would log every delegate assignment and outlet/property assignment, as well as every time each object in question is created and destroyed to see if the object addresses stay consistent or change when there is some event (like the crashes you experience). I would also make sure to set the delegate to nil when you expect the delegate to be destroyed, and outlets/properties of combo boxes to nil when they are expected to be destroyed. HTH, Keary Suska Esoteritech, Inc. "Demystifying technology for your home or business" _______________________________________________ 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/archive%40mail-archive.com This email sent to arch...@mail-archive.com
