RESOLVED: Custom par bug

Hi there,

I think I found a bug with custom par naming.
First I add a custom par named Testfloat1 and then another named Testfloat11.
The first one disappears, when I add the second one.
See attached toe.

Best wishes,
David
custom par bug.toe (3.44 KB)

Thanks for the report!

This is happening because the “replace” keyword argument to appendFloat is True by default. You get name overlaps: Testfloat1 creates Testfloat11, Testfloat12, Testfloat13, and Testfloat14. These name overlaps also happen with tuplet names, so creating Testfloat11 causes a replace even though the parameters created are actually named Testfloat111, Testfloat112 etc.

If you set the replace argument to False, you will get an error as expected.

This is not exactly a bug, but is undeniably a bit confusing!

This makes sense, thank you Ivan.
Though it is not really intuitive, that tuplet names and parameter names are overlapping…