Building from current source freezes on clip length changes/Current repo different than 1.04 source?

[nyboer]

I'm making some modifications for my own evil needs. I tried some with success, but noticed that when I change the clip length, it freezes with error: “continue_immediately” is not a supported value. Digging into it, I find these lines in "DrumSequenceMode.java":
private void adjustMode(final int notes) {
if (notes % 8 == 0) {
cursorClip.launchMode().set("play_with_quantization");
} else if (clipLaunchModeQuant.get()) {
cursorClip.launchMode().set("continue_with_quantization");
} else {
cursorClip.launchMode().set("continue_immediately");
}
}

When I look at the API docs, I see:
Possible values are: - default - from_start - continue_or_from_start - continue_or_synced - synced:

When I look at the source provided with the most recent 1.04 build, I see:

private void adjustMode(final int notes) {
    if (notes % 8 == 0) {
        cursorClip.launchMode().set("default");
    } else if (clipLaunchModeQuant.get()) {
        cursorClip.launchMode().set("synced");
    } else {
        cursorClip.launchMode().set("from_start");
    }
}

I'm confused why the latest repo from before the latest release is different from the latest release source, but I'm more confused about the values used in the source that do not seem to be part of the API! I can just change these lines in my branch ok, but would love to understand what's going on!

[ericahrens]

The values cursorClip.launchMode() accepts have changed over Bitwig Versions. What Bitwig Version are you working with?

[nyboer]

I'm on 5 something. I guess those values changed from api 17 to 18 - mostly I'm just confused why the code in the repo doesn't align with the latest release? It seems like it would be ideal to fork from the repo, rather than work from the source of the latest release!