By experimentation, I discovered that I can get the export to flash to progress a bit further. If I turn off the control bar and the information button, Salasaga will actually save a .swf file. However, the file does not play (it does have a color background). In the save process, I receive a new error message: ED380 "Something went wrong when opening the font file".
I will continue researching......
Hi Robert,
Thanks for the encouragement, and persistence.
Went looking in the source code for the conditions that generate those error numbers, and ED91 is very generic.
It pops up if there's been any other error during the .swf creation process.
So, the ED380 is a lot more helpful, and confirms a suspicion, as it's to do with Salasaga having an issue when trying to open the font file.
Most of the problems that people have like this, are to do with the installation paths for things (like the font files).
At a guess, I'm thinking salasaga isn't finding the font files that are installed with it.
It's pretty easy to find out for sure too.
First things first, we should probably cover the basics, just to be on the safe side.
- Which version of Salasaga is installed? I'm hoping for Alpha 4 here.
- Was it installed from a package, or from the downloaded source tarball?
- Is there a file called "DejaVuSans.fdb" on your system? (this is the specific font file Alpha 4 installs and uses)
If you're using Alpha 4, and you installed from source (which should have led to a definitely correct installation), and that font file exists, then the best way to progress will be to do a quick run time check of where Salasaga is looking for this.
Are you familiar with strace? It's a utility to capture every single system call used during the run of an application. (Heaps of output, but I find it very effective, and it's easy plus very effective for stuff like this.)
I would do this:
a) Start Salasaga, capturing what it's doing:
$ strace salasaga > salasaga.strace 2>&1
Salasaga will run a fair bit slower than normal, and strace will be generating a *large* amount of output into the "salasaga.strace" file.
b) Load your project file in Salasaga (File -> Open).
c) Export the project file to swf (so it looks for the font file, and generates the error).
d) Quit out of Salasaga.
At this point, strace will also quit, and you'll have a pretty large salasaga.strace file. It's all text, and is quite messy.
e) Do a search in this salasaga.strace file for mentions of the "DejaVuSans.fdb". That will show you the path Salasaga is using to find it, and it should also show any error message information that Salasaga hit when trying to access it.
From there, you should be able to check if the file really is on the system in the right place, and figure out a way forward.
Does this all sound workable to you?
Btw - My head space at the moment is in server side stuff, as I'm putting a lot of time into getting the server side components of Salasaga up and running. It's likely going to be at least a couple more weeks until the client side IDE gets worked on again (and the swf bugs get fixed unless super urgent).
