Forum Discussion
Fix dialogue that offers no choices: missing fonts
Hi CarlFink1,
Thanks for taking the time to share your feedback. I can see why you'd want more control in this situation.
From what you've described, it sounds like you'd expect more flexibility when Storyline can't find a font. Rather than only being able to acknowledge the message, you'd like options that let you decide how to proceed, whether that's selecting a replacement font, locating the missing font, or canceling so you can avoid making unintended changes to your project.
I'd love to learn a bit more:
- Can you tell me more about what you're trying to avoid when this message appears?
- What would your ideal experience look like when Storyline can't find a font?
- What would help you feel more confident proceeding when Storyline can't find a font?
Thanks again for taking the time to share your perspective. We really appreciate the additional context.
Hi, Luciana,
I used to design user interfaces. Having a dialog with no Cancel button is a big no-no, with the single exception of a messageBox where the user has no real choice but to acknowledge the modal dialog. (Adobe gets this wrong far, far too often.)When Storyline finds that a font is missing, it might behave like, say, PowerPoint. That is, it could ask the user to find the font on their system. It could let the user select the replacement font manually.
It could and should tell the user that if they close without saving, the Storyline file will not be damaged, but if they accept the substitution and continue working, the original font information might be lost. Many companies (like mine) have required official fonts, and if a Storyline file switched from our approved Helvetica Neue to Arial (for instance) I'd have to manually fix every single bit of text in the thing. Which is one thing I'm trying to avoid, to answer your original question.
Hi CarlFink1,
Thanks for explaining this in more detail. The example with your company’s required fonts is especially helpful. I can see how an automatic substitution could turn into additional rework if text throughout a project has to be corrected manually. I’ve shared this additional context with our product team.
One thing that would help us understand the impact a little better: how often do you or your team run into missing-font situations like this?
Thanks again for taking the time to walk us through the workflow and the risk you’re trying to avoid.
Oh, it's quite uncommon. I'm not in the department that has to test and fix/update courses developed by contractors and vendors, of course. They probably see it more often.
I just installed the August 4 update, which says it has an improved font substitution dialog. I haven't actually seen the new dialog yet.
