SC.NestedStore#lockOnRead, which defaults to YES, is much too aggressive, locking even on attempts to read non-loaded records. This causes problems if, for example, a nested-store record's not-yet-loaded toOne relationship is read (e.g. by being bound to a view), locking it and triggering a load in the parent store. When the load returns, the locked record triggers a full nested-store reset (failing meanwhile to notify the nested-store record instance that it has loaded), or errors out if anything, anywhere in the nested store has changed. This commit avoids locking nested-store records when read in EMPTY or BUSY_LOADING states. It also modifies the behavior of SC.Store#_notifyRecordPropertyChange, which is where chained store errors are thrown, to switch solely based on the chained record's editable state, and to avoid costly and blunt full-store resets in any case. This allows the parent store to correctly update nested stores when untouched and unlocked records are updated.
…asier to position things at each step. Refactors renderer to use stepPositions and improve performance.
… did not change, it would render the steps on the first update.
… easily target the nth choink.
…sitioning to correct for visual glitches caused with scaling transforms. Fixes the important half of #1213.
…turn off scroll event hijacking.
…uts, with which they presently conflict.
…view. Refactored the tests to use SC.ControlTestPane/
… child view notification optimization. Includes tests.
… edge regardless of the minimum. Includes unit test. Fixes #1129.
…e concise fillRatio.
…t exist. Adds a new optional method `layoutDependsOnSize` to SC.ChildViewLayoutProtocol that determines whether the child view layout plugin needs to re-run when the view's frame changes. This is required for flexible views that lay out their child views dynamically based on their size. Because the view's layout doesn't change even when its frame does, it otherwise would not re-layout the child views.
- Tidies up a la jshint. - Ensures that 100% of the available space is used up even with rounded layout values. - Fixes a bug where a right/bottom position could be a decimal (ex. 0.25) which becomes 25% not 0. - Adds support for maxWidth/maxHeight to constrain how much available space is used for the child view (allows following child views to use more).
…oFit, let any child not specifying a fixed dimension to fill the available space. To calculate the final dimension/layout, a new property "fillAvailableSpaceRatio" is used