public final class MorphTransition

Enables the image-snapshot path. Each (source, dest) pair is rendered once into an Image at initTransition() (clipped to the component’s own bounds; off-viewport children do not contribute pixels), then the tween draws those images at the interpolated (x, y, w, h).

Use this when:

• The source lives inside a scrolling container whose scrollX/scrollY would otherwise leak off-viewport child pixels into the morph (the cross-form morph clipping artifact).
• The source has children with dynamic content (a BrowserComponent, a video frame, a custom-painted background) that should be frozen visually for the duration of the animation.
• The source’s parent applies a clip that the layered pane wouldn’t replicate.

Snapshot mode is also required for the per-named-target #rotation, #scale and #opacity tweens to have a visible effect, since those transforms are applied while drawing the captured image.

Default is off to preserve back-compat with the legacy live-paint path. Always pair with a screenshot regression test (see scripts/hellocodenameone/.../MorphTransitionTest).

Steps the transition to a normalized progress t in [0, 1] without reading the animation clock. 0 is the source state, 1 the destination state; intermediate values are eased with the same ease-in-out curve the clock-driven path uses. The call is deterministic, repeatable and may move backwards, so it composes with a frame-export loop that renders the animation at a set of progress fractions:

MorphTransition t = MorphTransition.create(600).morph(element);
t.init(source, dest);
t.initTransition();
for (double f = 0; f <= 1.0; f += 1.0 / frames) {
    t.setProgress(f);
    t.paint(frameGraphics);
}
t.cleanup();

#initTransition() must have been invoked first (the AbstractTransitionScreenshotTest harness does this for you). Scrubbing and the clock-driven animate() lifecycle are not meant to be mixed on the same instance.