wxMASSManager

v1.1.1 7855323bc6

Version 1.1.1: bugfix update Stable

williamjcm released this 2020-06-21 08:52:26 +02:00 | 67 commits to master since this release

Fixes #10.

Downloads

Source code (ZIP)
1 download
Source code (TAR.GZ)
1 download

wxMASSManager-win64-1.1.1.zip
119 downloads · 3.8 MiB

v1.1.0 6f5b02b395

Version 1.1: Screenshots, renaming, and no DLLs. Stable

williamjcm released this 2020-06-20 11:42:26 +02:00 | 68 commits to master since this release

First, a word of warning:

All new features in this release are still somewhat experimental. If (or rather when) they break, please DM me on Discord (I'm part of the M.A.S.S. Builder community in the official Sekai Project guild), or open an issue here on GitHub.

Let's move on to the actual changelog, now.

Renaming M.A.S.S.es

I know the game already has that feature built-in, but I wanted to make my own out-of-game version. Please note that it'll have the same restrictions as the game itself, to prevent abuse.

This is the least stable feature in the manager, so don't forget to make backups of your saves!

"Where are my photo mode screenshots stored ?"

A common question on the official Discord guild, which now has an answer!

Well, the answer is just one small part of this whole new aspect of the manager (it's that last button in the column on the right), but it's there.

The list on the left shows all PNG files that are found in the screenshot folder and can be sorted with the radio buttons on the right.

The view button will open a resizeable window showing the selected screenshot:

(Sorry for the scrollbars, I haven't found a way to scale the image instead. 😅)

The delete button is self-explanatory.

While the file system watcher will monitor the folder, it sadly won't catch file edition and renaming events, just creations and deletions.

What about the DLLs ?

This is version 1.0 of the manager on dynamic linking:

And this is version 1.1 on static linking:

While you can leave the DLLs in the folder when upgrading, I recommend deleting them to clean things up.

Some more safety

A much more minor change, but deleting a M.A.S.S. in the staging area using the manager will now prompt for confirmation. Exporting still doesn't, though, because I forgot to add it.

Downloads

Source code (ZIP)
1 download
Source code (TAR.GZ)
1 download

wxMASSManager-win64-1.1.0.zip
138 downloads · 3.8 MiB

v1.0.0 78653e317f

Version 1.0: staging area and UI tweaks Stable

williamjcm released this 2020-01-16 09:36:46 +01:00 | 83 commits to master since this release

Staging area

Perhaps the biggest feature of version 1.0 is what I call the staging area, a folder to centralise M.A.S.S. files that aren't in a hangar.

New import/export system

The new import button is more-or-less the same as the old one, except you need to select both a hangar and a staged M.A.S.S. before you can click it. The old behaviour where it asks to select a file is now gone.

The export button is always active, even if the game is running, as long as you select a hangar, and will automatically export a M.A.S.S. to the staging area using a predefined filename. WARNING: This feature exports using a predefined filename (<SteamID64>_<M.A.S.S. name>.sav), and will overwrite data in the staging area without a prompt.

Also, both buttons got spiffy arrows showing which direction a M.A.S.S. will take if you click.

Staged M.A.S.S. deletion

Just press this button when a staged M.A.S.S. is selected to get rid of it. WARNING: This feature will not ask for confirmation.

Quick folder open button

If you're too lazy or too lost to find the staging area folder (hint: it's the staging folder right besides the executable), just click this button to open it in Windows' file explorer!

File watching

Just like the hangar view on the left, the staging area is also under the file system watcher's, well, watchful eye, and will get automagically refreshed when a file is added, removed, updated, or renamed.

GitHub link

Using wxWidgets' wxAdvanced library, the link in the text at the bottom is now actually clickable, and will bring you straight to the project's home.

What's next ?

Bug fixes if needed, potential translation support (#4), and maybe a feature many of you would love (#9).

Don't get too hyped, though, as the latter two will need a certain amount of research and testing before I'll be able to work on them.

Also, outside of bug fixes, don't expect fast progress or response times, as this application is just a side project I started to take a break from my main one.

Downloads

Source code (ZIP)
1 download
Source code (TAR.GZ)
1 download

wxMASSManager-1.0.0-win64.zip
141 downloads · 6.1 MiB

v0.2.0 cc0e6cedff

Backups, active slot tracking, safety measures, and optimisations Stable

williamjcm released this 2020-01-12 15:01:49 +01:00 | 99 commits to master since this release

File watching system

This is perhaps one of the biggest backend changes the app got between v0.1.1 and v0.2.0.

Now, instead of going through all hangars to see if there were changes, the manager asks the filesystem to send it updates for all the sav files in the save folder.

If a M.A.S.S. gets created, deleted, moved, or updated, only its corresponding line gets updated, reducing flickering caused by the constant re-rendering of the list items.

It also enables part of the next change, which is...

Active slot tracking

Now, you can see which hangar is the currently-selected one in your profile. And if the game is running, the above change allows it to update in real-time!

Sadly, due to how the game works, I can't make it changeable from the manager.

Backup zip creation

Thanks to this handy button, the manager will be able to automagically create a zip file containing your profile and M.A.S.S.es in the location of your choice.

A word of advice: backup early, backup often, and make multiple backups. Storing the zip files on a cloud storage isn't a bad idea, because the zips really small (less than a megabyte if all hangars are filled).

Game status indicator

Every three seconds, the manager will take a look at the list of processes running on your computer to see if the game is running.

If it's the case, all potentially-dangerous features (importing, moving, and deleting M.A.S.S.es) will be disabled in the manager.

If the manager can't access the list of processes for whatever reason, those same features will be disabled, because the game could be running.

Separation between GUI and backend

This optimisation is more for my workflow than anything. Prior to this update, the backend code was in the same file as the GUI event handling code, and it was on its way to become a maintenance Hell.

So, before it actually became a maintenance Hell, I separated all backend code from the GUI code.

It'll also be easier for me to add new features, like the upcoming staging area mentioned in issue #1.

Downloads