Messages

[EDIT:]

Update regarding viewports: in the end I just placed the contents of each save slot in a single Window_Scrollable, instead of drawing a set of windows for each. I had the feeling that the viewport issue was previously investigated, but it felt like the matter was dropped.

Also on the latter: MKXP is something I would greatly like to use, simply because multi-platform is a good idea, but I've never been sure how to make use of it - XP Ace uses a mix of RGSS1 and RGSS3, and there's no way to use both in MKXP. And of course, Win32API class support is out, which breaks XPA_Tilemap and XPA_Window. Never mind say, XInput support.
... I have no idea how to compile things, but I wonder if simply compiling a version of MKXP which always refers to XP's tilemap and window regardless of RGSS version would be a start...

Though regardless of RGSS setting, MKXP doesn't support OGG LOOPSTART. Loop points and remembering playback position of music after battle was what enticed me to VXA in the first place... before I realised how anxiety inducing the map editor would be.
EDIT: Actually wait it does support loopstart... if you also specify looplength. VXAce doesn't seem bothered by that, curiously, but I've found some other systems before require it.

[(@file_index * @height) - ($scene.file_index * @height)]

This system is a life-saver. Originally I started my project in RMXP, but then I was tempted by VXAce's engine in all the myriad of improvements it had. But god did I underestimate how much anxiety and frustration its mapping UI would cause. (why are there still not layer buttons in MV????)

So I went from XP to Ace and now to this. Now I have my project in XP with various things I've learned from Ace, along with engine improvements.
There is though one element that Ace improved on that I don't seem to see way to do here: Windows inside viewports.

In Ace you could use viewports to move sets of windows or display only portions of windows. You can't do that here - near as I can tell, setting an XPA_Window to be tied to a viewport doesn't change anything. I want to make a scrolling save file list, and I would do that by putting them in a viewport and scrolling that... but, no dice.
I can use viewports by using Ace's native Window module instead of XPA, but that seems to make padding fall apart, and I've made minor adjustments to the code for personal customisation, so I'd lose that.

For now I can just set co-ordinates for each window (i.e. (@file_index * @height) - ($scene.file_index * @height)), but I think the functionality of Ace viewports would still be an improvement.