Clip

Places a prebuilt HapticPattern on the timeline at the current position.

Signature

@Composable
fun JindongScope.Clip(pattern: HapticPattern)

Parameters

Description

Clip drops a self-contained pattern next to inline nodes. It is the bridge between a HapticPattern value, typically an algebra result built with buildHapticPattern, and the composable DSL. The clip's events are offset by the nodes that precede it, so it schedules relative to its position like any other node.

val heartbeat = buildHapticPattern {
    haptic(60.ms)
    delay(80.ms)
    haptic(40.ms)
}
 
Jindong(trigger) {
    Clip(heartbeat)
    Delay(200.ms)
    Haptic(60.ms, HapticIntensity.MEDIUM)
}

Freezing and re-firing

A clip captures its pattern at compile time. Because Jindong compiles content in a single pass with no recomposition (see The Reactive Contract), swapping the pattern in state alone does not update the clip. Thread the pattern through the trigger keys to make it live:

Jindong(pattern) { Clip(pattern) }

HapticPattern is a data class, so the key comparison is structural: an equal pattern does not re-fire, a different one does.

Usage

Composing with the pattern algebra

Clips pair well with the pattern transforms, which return new HapticPattern values:

val base = buildHapticPattern {
    haptic(50.ms)
    delay(50.ms)
    haptic(50.ms)
}
 
Jindong(speed) {
    Clip(base.timeStretch(1f / speed))
}

Reusing a pattern across screens

private val confirm = buildHapticPattern {
    haptic(50.ms)
    delay(50.ms)
    haptic(100.ms)
}
 
@Composable
fun SaveButton(saved: Boolean) {
    Jindong(saved) {
        if (saved) Clip(confirm)
    }
}

Notes

• The pattern is captured when the node is inserted, not on every frame
• Preceding Delay and Haptic nodes shift the clip's start time
• HapticPattern equality is structural, which drives key comparison
• An empty pattern (HapticPattern.Empty) places nothing

See Also

• The Reactive Contract
• Sequence
• Core API