It might simplify some xml structure if the switch action had two additional optional variables... tweentype and time.
Right now... if I want to do something like fade in / out an image... I have to create two different actions with the appropriate tweens. One for fading in... the other for fading out.
But, if we could specify the tweentype and time in a switch... then it could be simpler... from structuring the xml at least.
Of course, now that I am writing this, I'm thinking I might be able to do something similar, using a single action by passing variables %1 and %2 through...
