I've just wired up a 1200 pixel seed pixel prop and when I went to fit the pigtails I realised that I had inserted the full 1200 pixels in the reverse order. I didn't think too much of it as using Falcon player there's been a way for numpty's like myself who do this to reverse the string direction. I'm not using Falcon Player for this application and either I'm not holding my tongue right or the "Reverse" option in the xlights model data doesn't work as I expected. I kinda assumed that the string would be reversed at pretty much the output to lights point and that any submodels etc would still works the same. What I found was that the "reverse" appears to be implemented prior to the processing of any submodels. I've tried this on 2024.12 and 2024.13.
Below are screenshots of what the preview shows before and after selecting "reverse" on the model data page.
The prop that I failed on has dozens of submodels that I have created and a lot of the channel rages are in the 1-16 format rather than 1,2,3 etc if that makes any difference.
I can fix my screwup via some fiddling with numbers but I was hoping that I'd either found a bug/quirk in xlights or that I wasn't doing something right.
Below are screenshots of what the preview shows before and after selecting "reverse" on the model data page.
The prop that I failed on has dozens of submodels that I have created and a lot of the channel rages are in the 1-16 format rather than 1,2,3 etc if that makes any difference.
I can fix my screwup via some fiddling with numbers but I was hoping that I'd either found a bug/quirk in xlights or that I wasn't doing something right.