Simulating a command prompt- works well when previewed, but not when published.
Jan 04, 2018
Hi
I'm using Storyline 2 to simulate a command prompt. I'm happy with how it works when I preview, but there are several unwelcome changes when I publish to HTML.
I'd be grateful if anyone can help with the following issues, or even suggest if there's a better way to go about what I'm trying to accomplish.
1) My base layer font becomes fuzzy and grey.
Jpeg artifacts? Changing the published image quality to 100% didn't seem to affect this.
2) The cursor doesn’t appear in the input box.
The input box is on it's own layer which is timeline activated, as this should make sure the input box control gets focus
3) The trigger fires after a single character is input
This shouldn’t occur until control loses focus.
4) The triggered ‘response’ layer is the wrong font.
The text box is set to Lucida Console. The default player font is Open Sans. When the response layer opens, the displayed font is neither of these. On the positive side, though, it's nicely bright and crisp.
2 Replies
Hi Chris,
How does it look when you publish to Flash? Because if it works perfectly fine in preview and in Flash output, then the problem may lie in the HTML5 output of Storyline 2.
Here's a link to a chart that explains what does/doesn't work in HTML5 output in Storyline 2: Comparing Flash, HTML5, and Articulate Mobile Player Output
For what it's worth, all of these problems with HTML5 have been fixed in the newer versions of Storyline (Storyline 360 & Storyline 3). You can download a free trial of either of these if you're interested in seeing how it works. You can open your existing Storyline 2 files in either of the new versions.
Nicole
Hi Nicole
Thank you for pointing me in the right direction.
This is indeed an issue with HTML 5. I was trying to view the Flash version, but Firefox was opening the HTML5 page instead.
In order to view the Flash version in Firefox (57.0.4), the plugin option to "Block dangerous and intrusive Flash content" has to be disabled.
Rather thank ask users to modify their security settings, I think I'm going to have to try and find an HTML5-compatible approach instead.
Chris
This discussion is closed. You can start a new discussion or contact Articulate Support.