Pain and humiliation. I had moved things around and put rotationControl in a new place. However, I failed to @synthesize it, so it was lumbered with rotationControl and _rotationControl. Fixed that, works just as it should.
Thanks to several of you for the attention. David On Aug 22, 2013, at 3:19 PM, Quincey Morris <quinceymor...@rivergatesoftware.com> wrote: > On Aug 22, 2013, at 13:42 , David Rowland <rowla...@sbcglobal.net> wrote: > >> Good suggestion, but such is not the case. Most strange is that when I set a >> breakpoint and use control-click to print a description of rotationControl >> to the log, it shows a valid non-zero frame although qframe is zero. I have >> checked for zombies, but none reported. > > One thing to keep in mind is that "frame" is a *derived* property in iOS. > Further, its value is meaningless if the view's transform is anything other > than the identity. > > If you're seeing weird values for "frame", your very first strategy should be > to examine "center" and "bounds" separately. If they contain the expected > values, then there's probably a good reason why "frame" is meaningless in > your scenario, so don't use it. If they don't, you know that you need to look > at other factors to determine what's going on. > > In your scenario, though, perhaps "rotationControl" actually uses rotation of > its own visual appearance to represent its own value. In that case, setting > its "frame" property isn't going to work. > _______________________________________________ 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
