@chchwy Thank you for getting March 9th Nightly build out
With that said I feel some issues that appear as “fixed” should not be linked in the Fix description because they are either not fixed or they weren’t really ‘bugs’.
So in order to warn other users when they are using this new Nightly Build i’ll write an ‘errata’ for the release notes below:
Issue #453 was closed not because it was fixed but because it was a duplicate of issue #289 which remains open.
So the sound problem has NOT been actually fixed. In fact in MArch 9th 2016 Nightly Build there’s a severely critical problem now where if you create a new sound layer, save the file and reopen the sound layer is gone. And to make it worse if you import a unique sound into that layer, once you reopen the actual sound file will be deleted from the computer! I just lost a test file like that, but if other users utilize this without warning they might lose their songs or unique files without warning! (I’ll report it properly later on)
Also Issue #449 was more like a question than a fix, because the user didn’t understand how to use the onion skin visualization feature and didn’t ask in the forum before reporting, so it shouldn’t be counted as a “fixed” problem, because there never was a problem to start with.
Issue #424 is fixed via #433 AND #436 was actually fixed via #456 which is not included in the notes. The layer management system still has a leftover minor bug which I will report soon, as it is related to this.
Issue #429 was a feature request that was ultimately dropped (hence it was closed), so it shouldn’t be counted as a “fix” however the idea still lingers in issue #391 which addresses similar features to favor unifying the selection and move tool into a single tool.