Quote:
Originally Posted by Ephemerality
A new version has been uploaded to the first post, marked "BETA KFX"
|
Well a huge and mighty thank you for coming back to me on that issue. To be honest I haven't been expecting a reply anymore :-). So it's even more fantastic that you manages to come up with a working beta this quickly.
The great news is, it generally works really well. The allocation of the Characters to the position within the text seems to be on the spot now. I tested with a couple of books and there wasn't a single position mismatch.
There is however a little Issue with manually edited aliases. Since Goodreads usually provides - if anything - the caracter names without any aliases or description I tried to pull an XML off an existing Original Amazon X-Ray. But the "X-Ray Terms Creator" seems to be omitting all the aliases. They won't get saved into the XML nor into the .aliases File. They are however shown in the list before saving. Most of the times however, when trying to save the file, the programm throws an exception alltogehter
Code:
the object reference was not set to an object instance.
at XRAYBuilderGUI.UI.frmCreateXR.CreateTerms()
at XRAYBuilderGUI.UI.ftmCreateXR.btnSaveXML_Click(Object sender, EventArgs e
It happens more frequently the more complex the List gets. It mostly works when I compile a handmade list with only a couple of Entrys and no Description. My first thought was it might be an issue with special characters since I used a german X-RAY File. But it's all the same with the English one.
So what I could do is pull the XML off an existing X-Ray and manually compile the aliases-File. It's a buttload of work so I did it just once for testing purposes. It worked however like a charm and a huge amount of occurenced were found. I freqently encounter errors like this while compiling the X-Ray:
Code:
An error occurred while searching for start of highlight.
Was looking for (or one of the aliases of): <name>
[rather long text excerpt]
But it doesn't affect the other occurences and the XRay still renders properly. So it might just be an occasional flaw with no functional impact.
I really hope it requires only a minor fix to the Terms Editor. I will be happy to provide you with my samples if you tell me how.
But the good news is, since the positioning issue seems to be solved, XRAYs for KFX might just be a few steps away from beeing perfect. GREAT WORK!!!