Forum Discussion
OstbergM
10 years agoStaff
Hello there,
No, unfortunately JavaFX2 needs to be started in order to provide charts for reports.
There is a workaround however, but it might take a few steps to resolve.
First off, the error you are seeing is related to your system not having any TrueType fonts, which is okay, since you are running CentOS.
So what LoadUI does is that it tries to install a TrueType font from the bundled $LOADUI_HOME/jre/lib/fonts/*.ttf i think into the user home-folder if any.
What you can do, is to make sure that your user has access to and that loadui can write to ~/.fonts and can run a command called 'fc-cache -v'.
I'm going to refrain from suggesting what package includes it since it varies depending on OS version and is very easy to look up.
This will allow it to copy the *.ttf files to that folder and import them into the systems font-cache, which in turn instructs JavaFX2 into believing that the system has the fonts that it will need.
An alternative if you are unsure whether loadui should have access to the folder is to manually copy the .ttf files to a folder which fc-cache -v checks, it is very verbose about it, and run fc-cache yourself after it is copied.
I hope this resolves your issue!
If not, respond to this thread and we'll work something out.
Best regards,
Mikael
No, unfortunately JavaFX2 needs to be started in order to provide charts for reports.
There is a workaround however, but it might take a few steps to resolve.
First off, the error you are seeing is related to your system not having any TrueType fonts, which is okay, since you are running CentOS.
So what LoadUI does is that it tries to install a TrueType font from the bundled $LOADUI_HOME/jre/lib/fonts/*.ttf i think into the user home-folder if any.
What you can do, is to make sure that your user has access to and that loadui can write to ~/.fonts and can run a command called 'fc-cache -v'.
I'm going to refrain from suggesting what package includes it since it varies depending on OS version and is very easy to look up.
This will allow it to copy the *.ttf files to that folder and import them into the systems font-cache, which in turn instructs JavaFX2 into believing that the system has the fonts that it will need.
An alternative if you are unsure whether loadui should have access to the folder is to manually copy the .ttf files to a folder which fc-cache -v checks, it is very verbose about it, and run fc-cache yourself after it is copied.
I hope this resolves your issue!
If not, respond to this thread and we'll work something out.
Best regards,
Mikael