Yes, both installations are Alpha 4 version, so it is possibly caused by the internal memory corruption.
But starting from command line with -d only show this:
Debugging mode, errors will be shown on stdout.
Program path: 'salasaga'
Directory base: '.'
Icon path: //usr/share/salasaga/icons/72x72
Path to mouse pointer image: //usr/share/salasaga/icons/scalable/pointers/standard.svg
And that's with a fresh started installation, no swf export or anything, only opened the project file. And Salasaga shows none of the Fade Out's from the project file.
Strange that it happens when opening a file and not when saving, which is the more "normal" way these values gets lost.
I will compile the Alpha 5 version within a day or two and how that goes.
Meanwhile the list of other bugs I have, stays with me, just in case they are closed in the Alpha 5 version.
Yes, both installations are Alpha 4 version, so it is possibly caused by the internal memory corruption. salasaga/ icons/72x72 salasaga/ icons/scalable/ pointers/ standard. svg
But starting from command line with -d only show this:
Debugging mode, errors will be shown on stdout.
Program path: 'salasaga'
Directory base: '.'
Icon path: //usr/share/
Path to mouse pointer image: //usr/share/
And that's with a fresh started installation, no swf export or anything, only opened the project file. And Salasaga shows none of the Fade Out's from the project file.
Strange that it happens when opening a file and not when saving, which is the more "normal" way these values gets lost.
I will compile the Alpha 5 version within a day or two and how that goes.
Meanwhile the list of other bugs I have, stays with me, just in case they are closed in the Alpha 5 version.