Version 0.3.x series achieved!
kagestudio_v0.3.200411_win64.zip
Still a late-ALPHA or early-BETA release but still a good progress. As most backlogs for v0.3 has already been implemented in previous release, didn’t really expect to implement last few needed changes in achieving version 0.3 soon given the difficulty compared the first set of v0.3 backlogs done.
Demo, you say? Have you seen this timelapse of me illustrating a frame from Your Name (Kimi no Na wa)‘s MV.
For overview, I’ve published the project’s Roadmap last week. And if you check the roadmap, you can see v0.3 is just the first half of v0.8. Nonetheless, just got more time to start working on v0.4 backlog (which is basically the second half of v0.2 backlog).
Of course, this release isn’t bug-free just yet. That means v0.3 will be in Maintenance Mode and will probably have several bug-fix releases before v0.4 comes out.
~creek23
UPDATE: Originally released a very buggy v0.3.200410. Had to re-release 0.3 series with v0.3.200411
Changelog:
– fixed KageFrame::isEmpty()
– fixed canReUseNextFrame (previously, canDuplicateNextFrame)
– fixed Makefile.gnu to properly compile
– implemented saving/loading of Frame extension
– implemented Remove Frame
— different to Delete Frame which deletes content of Frame
— Remove Frame decreases number of Frames from the last
– made Add Frame to add New Frame if Next Frame is not reusable (empty/extension)
– made New Layer get focus after Layer->Add
– revamped handling of switching frames
– removed constraint on Cut/Copy/Paste since Copying/Pasting Frames have different shortcut key (Ctrl+C vs Ctrl+Shift+C)
– added Onion-rendering if modifying shape
– added File->Close as alias of File->New
– added propmpt before New/Close if current content is unsaved
– added Doxygen file for dev docs
– removed use of KageFramesManager::currentFrame
– moved split/trim to StringHelper
– renamed framemanager.cpp to frameset.cpp to avoid confusion with framesmanager.cpp
Leave a Reply