Be notified of new releases
Create your free GitHub account today to subscribe to this repository for new releases and build software alongside 36 million developers.Sign up
Demetrius found a bunch of critical issues that automated testing still isn't covering, so I've fixed them.
Hopefully this time things will be fine?
--- THIS IS BROKEN. PROBABLY BEST TO USE THE LAST ONE. ---
The helpfiles are probably still somewhat broken after this one, I may have forgotten to update them properly, but, hopefully this should make the UI less of a maze.
This fixes various problems with save file editing, general stability, adjusts/adds a few features, and various other vague stuff I forgot.
NOTE! The old PathSyntax/ValueSyntax has been disabled. This probably won't break too much but it's another stepping stone before RFG finish what they're up to and I end up having a ton of JSON schemas to write...
With any luck this should help get rid of some of the weirder syntax nonsense in R48.
As usual, thanks to Demetrius (@rohkea) for testing, & various ideas that went into this release, such as the mechanism to select an entire indented block.
This deals with at least the major bugs that were in v1.1.
Thanks to @rohkea for finding the majority of the bugs.
(v1.2 will actually focus on usability issues, BTW.)
v1.1 marks the changeover to the newer UI system in the gabien-common library, which is a lot better at handling, say, changing text sizes. Or text sizes in general.
Hopefully, the layout bugs will be gone after the rather long amount of time I've
been busy doing other stuff had to work on this release.
...In case of issues, I suppose try v1.0-3?
NOTE: There is a problem with this build where the "Resize" tool on maps is totally non-functional. Please instead go into Properties,
@data, and modify the size from there.
Hopefully the XP schema should be fixed by now, but more testing required.
In particular it might turn out the update to the way the CommonEvents is handled (changed to Ix1, which makes sense but might be wrong) was a bad move.
This contains a few bugfixes, like stopping the "rectangle" tool causing the pen to disappear, a better understanding of tables and their dimension count, and keeping the information on the currently selected tile for when the user changes layer.
This release is arguably worse than the previous release. Don't touch it.
Yes, this means you'll have to live without VXA map creation while I write - and try to put more testing work into - v1.0-2.
v1.0's accidental 4D tables are correctable and relatively data-safe. v1.0-2's various breakages are probably not.
* Not a solid year, but it has been a year since R48 started being written. Check commit dates for more information.
As a reference point, this version uses:
gabien-common 45dd312363b80658c23ac6b939341636b4eceb71 gabien-javase 829bcbe084e2f4a0dfdbb65cbaab225c14bd36bb gabien-android ff237e180cf6731b2a78fde055d5b954242c161c