Just stumbled across a workflow that seems to cause this script to zap a folder from existence. Try this:
Create 3 tracks.
Name tracks 1-3 "Uno", "Dos" and "Tres" respectively (just seems easier to describe this with track names instead of numbers).
Make Uno a folder, and Tres the end of the folder.
Select Dos and run "Move selected tracks down on visible track list.lua". The track moves down as expected, and the end of folder is correctly reassigned to Tres, which is now track 2. But...
Now select Tres and run "Move selected tracks down on visible track list.lua" again. This time, Tres moves down as expected, but the folder routing disappears entirely.
Thanks in advance if there's anything you can do to tighten this up.
Hi X-Raym,
Just stumbled across a workflow that seems to cause this script to zap a folder from existence. Try this:
Create 3 tracks.
Name tracks 1-3 "Uno", "Dos" and "Tres" respectively (just seems easier to describe this with track names instead of numbers).
Make Uno a folder, and Tres the end of the folder.
Select Dos and run "Move selected tracks down on visible track list.lua". The track moves down as expected, and the end of folder is correctly reassigned to Tres, which is now track 2. But...
Now select Tres and run "Move selected tracks down on visible track list.lua" again. This time, Tres moves down as expected, but the folder routing disappears entirely.
Thanks in advance if there's anything you can do to tighten this up.