…om a SC.ScrollView pinch-scale gesture.
- Scroller max values now update during touch scaling. - Bouncing back from out-of-bounds scales now position correctly. - Views can now animate back along an axis whose canScroll property is false. - Handling of subsequent touches after the initial one is captured by the content is improved.
…tic positioning of the content.
…crollView content view scroll transforms.
- Fixes responder chain bug that was preventing the content view from ever getting a swing at touch events. - Fixes a ScrollView bug where child view tiling was failing to trigger min/max recalculations when it caused a container view resize. - A number of unit tests were failing because SC.ScrollView now updates its layer asynchronously. Fixed these by cheating and triggering the update synchronously.
- Improves scrolling performance with requestAnimationFrame. - Implements touch kinetic scrolling and scaling. Working on #1267. (A number of bugs and bounce-curve improvements remain to be made.) - Improves SC.Touch documentation. - Adds a number of new SC.ScrollView properties to control various aspects of touch scrolling (e.g. direction scroll tolerances and locks). - Cleans up old touch-scrolling methods from SC.CollectionView, SC.ScrollerView and SC.MenuScrollView.
… method. The SC.$.view() method was called excessively by SC.RootResponder to find the target SC.View instance for events, but was wasteful as it requires creating an Array in jQuery only to ever use the first item. SC.viewFor method does the same thing about three times faster.
…Observable using @if(debug).
…up when changed.
… `unloadRecord` on children and `unregisterChildFromParent` on the parent.
storeKey, even if it is not a child record.
The previous commit incorrectly calculated which records to unregister and register. All items after the passed in index need to be unregistered, then all the new items should be registered, followed by the existing items that were previously unregistered.
There were a couple of issues with unregistering nested records: 1) SC.ChildArray did not unregister nested records at all, so toMany relations with nested records did not work properly. 2) When a child was unregistered from its parent, that did not propagate to children of the child, leading to problems when nesting was several levels deep. 3) There were two additional caches that were not being cleared when the nested record was unregistered.