This pull request implements two improvements to rendering:
First, instead of being a static size, the nameplate box now adjusts its width to fit the name of whoever is speaking.
Second, it tries to use the nameplate font recreation discussed in issue #22 before falling back to the other fonts.
To do the dynamic nameplate sizing, I did my best to recreate the dialogue box based on screenshots from the original DS games.
Here is a screenshot of a quick test dialogue before the pull request:
And this is what the same dialogue looks like with these changes:
In order for this to work, some additional assets will need to be added to the assets folder. This zip file includes:
ace_name - folder with the font discussed in #22 for the nameplates
textbox - folder with the PNGs for the text box and nameplate parts
AA dialogue box recreation.afphoto - the raw Affinity Photo document with the dialogue box. If you'd like it in another format like PSD, I can certainly export it, but I don't know if any data will be lost.
They should just need to be placed in the assets folder (with the exception of the .afphoto file; it's just there so we can edit it later :) )
I've tested this with the example.py file as well as a few of my own short scripts, and it seems to be working well, but of course it'd be great to have other checks done before merging so it doesn't break anything.
This pull request implements two improvements to rendering:
To do the dynamic nameplate sizing, I did my best to recreate the dialogue box based on screenshots from the original DS games.
Here is a screenshot of a quick test dialogue before the pull request:
And this is what the same dialogue looks like with these changes:
In order for this to work, some additional assets will need to be added to the assets folder. This zip file includes:
ace_name
- folder with the font discussed in #22 for the nameplatestextbox
- folder with the PNGs for the text box and nameplate partsAA dialogue box recreation.afphoto
- the raw Affinity Photo document with the dialogue box. If you'd like it in another format like PSD, I can certainly export it, but I don't know if any data will be lost.They should just need to be placed in the
assets
folder (with the exception of the.afphoto
file; it's just there so we can edit it later :) )I've tested this with the
example.py
file as well as a few of my own short scripts, and it seems to be working well, but of course it'd be great to have other checks done before merging so it doesn't break anything.Thanks so much!