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
Debugging into the used SequentialLayout shows that there are still three views in the ViewSequence, after invoking View.destroy() after transition end.
The code path from meteorFamousView.js with all the TODO is taken in my example.
// If we're part of a sequence, now is the time to remove ourselves
if (fview.parent.sequence) {
if (fview.sequence) {
// TODO, we're a child sequence, remove the child (TODO in sequencer.js)
// log.debug("child sequence");
} else {
famous.core.Engine.defer(function() {
fview.parent.sequence.remove(fview); // less flicker in a defer
});
}
}
The text was updated successfully, but these errors were encountered:
Flawed logic on my part :( Removing child sequences isn't so urgent/important, but the if condition should have always removed the child until the other code is written. Fixed, made that clearer, and will be in 0.1.31.
* Bugfix (#famous regression): Revert back to Blaze.render (for non-Surfaces)
to ensure rendered callbacks of nested templates are correctly run (#199)
* Bugfix (#famous regression): direction="1" now works again (#207)
* Bugfix (#RenderController): fview._transition is now properly honoured (#193)
* Bugfix: `fview.destroy()` now correctly removes children from
child sequences (#153)
* Enhancement (#famousEach): Allow overrides on all famousEach observe within
the containing fview. See Views README for details. (#201)
* Enhancement (#Surface): watchSize now uses javascript-detect-element-resize
lib to detect size changes on
* Enhancement (#Surface): Defer running of Surface rendered callbacks for
smoother performance.
When removing one middle column [-] in the #Animate example there is always a small white gap between the remaining columns.
http://meteorpad.com/pad/rXrmAYnMtuP7rnFeD/#Animate
Debugging into the used SequentialLayout shows that there are still three views in the ViewSequence, after invoking View.destroy() after transition end.
The code path from meteorFamousView.js with all the TODO is taken in my example.
The text was updated successfully, but these errors were encountered: