New Member
It's probably not hard to code into an interface then.
You could add other code strings in there too, like how much the song loops, whether it stops when you're out of transformation, etc.
Like modify the Playlist editor to incorporate options for altering the XML coding. I right click a song, I choose the option for apply to transformation, and then I pick the transformation from a list. There could be a separate window displaying all of the transformations and current songs on them. It'd save everyone the trouble of having to learn what XML is and what lines to edit. It'd save them time from having to change it around if they didn't like it or wanted to change up the songs often.
And on top of that, you could allow people to restore default or save different settings on it so they can switch quickly between them. Maybe two people use the same computer and they like different music.
You could add other code strings in there too, like how much the song loops, whether it stops when you're out of transformation, etc.
Like modify the Playlist editor to incorporate options for altering the XML coding. I right click a song, I choose the option for apply to transformation, and then I pick the transformation from a list. There could be a separate window displaying all of the transformations and current songs on them. It'd save everyone the trouble of having to learn what XML is and what lines to edit. It'd save them time from having to change it around if they didn't like it or wanted to change up the songs often.
And on top of that, you could allow people to restore default or save different settings on it so they can switch quickly between them. Maybe two people use the same computer and they like different music.
Last edited: