well you need to take a look at the TweenAnimation Script inside indeed.
This is the core of it :
Code:QueueTweenAnimation.prototype.initialize = function(translate, scale, rotation, frame, curveType, coordinateType)
when translated:
Code:this._theAffectedWindow.addAnimation(new QueueTweenAnimation(new Point(x_pos, y_pos), new Point(x_scale, y_scale), end_rotation, time_frame, curve_system, coordinateType?));
Wow, I haven't been using RMMV for a while, but I'm finally dipping back into it and remembering where I left off! Thanks for the reply! That all makes sense, though I'm not sure how or where to apply that last line of code. I'm assuming I'd fill in the values, like:
Code:this._commandWindow.addAnimation(new QueueTweenAnimation(new Point(32, 32), new Point(100, 100), 0, 300, curve_system, coordinateType?));
except I'm unfamiliar with the last 2 values. It's too bad there's no easy spot for me to see the starting position, etc. per window to their end position, etc. Then I'd know exactly what to change, haha.
EDIT: Sorry! Spoke too soon! I see PD_MenuSlide is what I should be messing around in, haha. Thanks! We'll see if I get it working.
EDIT EDIT: Got it! It's weird. I had to make my windows x and/or y values be at the starting point of the animation in the scripts I've got for the custom menu and then in the PD_MenuSlide I set the distance to be the difference from the starting point to the end point.