You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This refactoring introduces a backwards incompatible API change: the `alwaysShowTouches` and `showTouchesWhenKeyboardShown` properties are now gone, and the semantics of `showTouches` has changed.
`showTouches` is now more predictable and reflects whether touches are being rendered or not. `alwaysShowTouches` is sort of replaced by `automaticallyManageTouchesWhenScreenMirrored`, which, if YES, will automatically set `showTouches`.
Added a notification (QTouchposeTouchesVisibleDidChange) for monitoring changes to `showTouches`.
This resolves#16 and resolves#11.
All properties of retainable object type now explicitly specify their ownership (strong, weak, ...), but no guarantee that this mixed ARC/non-ARC code will work. At this stage, hopefully everybody is 100% ARC.
I think you want "strong" on this property attribute, no? I'm getting a warning in xcode 5.1 with mixed arc/non-arc code.
@Property (nonatomic, strong) UIImage *customTouchImage;
The text was updated successfully, but these errors were encountered: