Details
Bug
Major
Description
A form member has noticed while running the ViewerComponentExample.java example using the PRO version of the product content was missing.
I've taken a closer look and it a appears the FontManager is not being correctly initialized if the FontPropertiesManager is not being initialized.
I've taken a closer look and it a appears the FontManager is not being correctly initialized if the FontPropertiesManager is not being initialized.
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
The reason for this behavior is someone related to some customer changes related to font loading locations. A new init method has been added to the FontManger so that when accessed From the Font class we can insure the file file list has been properly created even if the FontPropertiesManager isn't being used.
Show
Patrick Corless
added a comment - The reason for this behavior is someone related to some customer changes related to font loading locations. A new init method has been added to the FontManger so that when accessed From the Font class we can insure the file file list has been properly created even if the FontPropertiesManager isn't being used.
Marking as fixed.