Fix T100918: change min value for NLAStrip start

The bug was contained in BKE/intern/nla.c, where the wrong macro was
used as the minimum frame value. Instead of `MINAFRAMEF`, `MINFRAMEF`
was used (the former is around -10k, the latter is 0, both fp32).

Differential Revision: https://developer.blender.org/D15940
This commit is contained in:
Thibault de Villèle 2022-09-12 17:07:29 +02:00 committed by Sybren A. Stüvel
parent 0759f671ce
commit 7c33d7b4b5
Notes: blender-bot 2023-02-14 03:46:57 +01:00
Referenced by issue #100749, Blender LTS: Maintenance Task 3.3
Referenced by issue #101368, NLA editor does not allow moving strips to negative frames.
Referenced by issue #100918, Regression: The start frame of NLA tracks can not be negative.
1 changed files with 1 additions and 1 deletions

View File

@ -1241,7 +1241,7 @@ static NlaStrip *nlastrip_find_active(ListBase /* NlaStrip */ *strips)
float BKE_nlastrip_compute_frame_from_previous_strip(NlaStrip *strip)
{
float limit_prev = MINFRAMEF;
float limit_prev = MINAFRAMEF;
/* Find the previous end frame, with a special case if the previous strip was a transition : */
if (strip->prev) {