Closed tomara-x closed 2 years ago
Thanks for the detailed report, I will investigate.
So there's a couple problems I see that seems to stem from a bad condition where the inserted points don't get sorted correctly which then messes up further point handling logic. I put in a fix for the second error stack trace (in git now), but it doesn't address the primary issue. This area of code was a bit tricky to implement the first time around but maybe a second pass now through will yield a clearer way to implement this.
thank you thank you! i gave the build a test, tried to be harsh with it as much as i could. your fix seems to have fixed the disappearing points issue. it does however manage to do this:
i assume that's the sorting issue?
Yeah, that's exactly it. If a point doesn't get sorted correctly it puts the line in a bad state. (bad connections in the first line in the image)
I believe the points should now be fixed up to maintain line integrity. Will be released in 2.8.2.
while moving the last point as shown in the picture, all the points to its left started disappearing:
i played around until it happened again and took a screenshot:
and blue was very unhappy about something:
after clicking around some more it just works normally but those points are gone
(ctrl-z doesn't get them back)it does actually edit: apparently this only happens with BSB objects that has a resolution setting (like the sliders) and while the snap function on the score timeline is activelog file: