Refactor internal handling of the waiting vs. ready state for controls #435

Merged
merged 3 commits into from Feb 24, 2014

Conversation

Projects
None yet
2 participants
Owner

bruth commented Feb 24, 2014

When control.ready() is called, two events are now called beforeready
which is called prior to the deferred object is resolved and ready which
is called after the deferred object is resolved.

The initial state of the control and binding the context occur during the
beforeready event to ensure other views can bind to the ready event
(or deferred object) once everything is setup.

Fix #434

bruth added some commits Feb 24, 2014

Refactor internal handling of the waiting vs. ready state for controls
When `control.ready()` is called, two events are now called `beforeready`
which is called prior to the deferred object is resolved and `ready` which
is called after the deferred object is resolved.

The initial state of the control and binding the context occur during the
`beforeready` event to ensure other views can bind to the ready event
(or deferred object) once everything is setup.

Fix #434

naegelyd added a commit that referenced this pull request Feb 24, 2014

Merge pull request #435 from cbmi/issue-434
Refactor internal handling of the waiting vs. ready state for controls

@naegelyd naegelyd merged commit 1dcf334 into 2.2 Feb 24, 2014

1 check passed

default The Travis CI build passed
Details

@naegelyd naegelyd deleted the issue-434 branch Feb 24, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment