I just thought of a partial solution to avoid this problem: obligate to expand all tracks and groups and subgroups before removing them.But this should not be necessary.Something happens with the collapsed groups that should be solved.
EDIT : Oops!Maybe this is not possible either because of the same error.
Well then, temporarily expand it before?
It’s not working either.It is as if being a collapsed main group with some subgroup inside, the collapsed main group “is locked” or does not work well under the hood of Renoise.That’s why I think something is not working right.And it does not depend on the API Lua, is something internal of Renoise.I could do what it says 4Tey but that would be like a patch.
And erasing or doing anything iterating forward or backward, should work the same way both ways, because you are only playing with an index (positions).It is for all I have pointed out that it may be appropriate to revise it, because the operation is not consistent.
In other words, Renoise v3.1.0 with collapsed groups with other groups within generates problems, maybe related to this new bug fixed here recently(various bugs with cloning groups).It is possible that after this arrangement, it already works well. But perhaps it would be appropriate to review it, before launching a new version.I guess soon we will have a version 3.1.1, with bugs fixed.For being a recent case, that’s why I comment.The related bug was solved a few days ago.
Take a deep look at this, please, Danoise, Taktik, etc.
Ah, OK. Yes, some quirks were discovered when duplicating groups. Maybe a similar thing happens when removing?
Will need to take a look at this as well.
Yes, that’s it!
But otherwise, what I said still holds true: when you’re removing items from an array that you’re also iterating through, you need to use a reverse counter or ripairs (“reverse ipairs”).
Okay, I’ll keep this in mind too.
Thaaaaaanks!!! 