Thanks for the suggestion. Usually I only put identifiers on views that need them for functionality at runtime, such as table column views and tab view items. It hadn't occurred to me that error messages might refer to them.
As to my question, I thought on it overnight and figured out that the only affected constraints would be those from any view in the affected scenes to their superview in the view hierarchy. That will substantially simplify the repair job. I'll try that later today and hope I'm right. > On Mar 15, 2016, at 3:46 PM, Lee Ann Rucker <lruc...@vmware.com> wrote: > > Start by giving all your views identifiers, that'll make them easier to track > down; the error message will use the name and you can search for it in IB. -- Bill Cheeseman - wjcheese...@comcast.net
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list (Xcode-users@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to arch...@mail-archive.com
