Font Change within a Text Entry Field

No matter what i do to the font and font size of the text within a text entry box, it always reverts back to the Articulate font, 12 point.

I've already noticed there are two ways to edit the font: You can click on the box and change the font, or you can edit the text and then change the font.

I've done both and every time it reverts back to Articulate 12pt.

Is this a bug?  What's the work around?  Highly annoying!

195 Replies
Jennifer Ritter

I am also experience the originally posted issue (text in data entry fields returning to Articulate 12 pt after edits have been made).

I've found that if I can get one data entry field to have the settings I want (using the workarounds) I can then use the format painter to apply those settings to other data entry fields. So far they seem to stick, both in Preview and after the course has been published.

Figured I'd share in case it works for someone else.

Matthew Womack-Evans
Alexander Salas

BTW- My only work around is to have no label on the field and add a separate textbox that acts as the label.   Then, I just added a state trigger to hide the "label" textbox when the user click on the TextEntry field.

I too am using Alexander's workaround which seems to be doing what I want it to. Another potential option is to create a default value for your variable (for use as a prompt) instead of the separate "label" textbox Alexander mentions, i.e. insert a default value of "Insert name here" (or whatever). This then shows in the data entry field when previewing/publishing the project until the user overwrites the variable. 

The problem with this is that when the user click in the data entry field they will have to manually delete the default value ("Insert name here") before entering their own values. I prefer the functionality of Alexander's option but this may work for what some people want to do without having spare textboxes sitting around.

Paul B

This is a significant bug, and what frustrates me the most is that it has persisted for years.

Not only is it annoying, this particular product flaw makes development of simulations that require data entry, cumbersome and time consuming. None of the "customer based solutions" (while appreciated) have worked for me...and I have tried them all.

I find it quite unacceptable that Articulate has not addressed this issue; I sincerely hope it is resolved soon.

Ashley Terwilliger

Hi Paul,

I don't know if you've had time to review this thread in it's entirety (it's a bit long, so I totally understand if you didn't!) but the issues were not consistently reproducible based on the initial postings here. We were able to reproduce them recently and as such reported it to our team and have included a link to this thread in the report with our QA team so that they're aware of the number of users being impacted. I'll be sure to provide an update in regards to the situations once I have additional information to share but I'm unable to offer a time frame in regards to that.

If you'd like us to confirm that your currently situation matches the issues identified in this thread, please feel free to share your .story file with our team here and describe what you're seeing vs. what you'd prefer to see. 

Paul B

Hi Ashley,

I would like to share the file, but company policy won't allow it.

I have read quite a few of the postings in this thread and my issue matches those where the font reverts back to 12 pt whenever a text box is selected. This is particularly annoying because for my applications I have to adjust the position of Storyline text boxes to match up with the software fields I am simulating...and I can't position the text boxes until the font size and type is correct. As soon as I move the text box...it reverts back to the default font. Saving the text box with as a new default is inconsistent (works sometimes...sometimes not). Consequently, it is very difficult to produce the effect I need. 

Hopefully we will hear an official solution from Articulate soon.

Thanks

DJ Trent
Paul B

This is a significant bug, and what frustrates me the most is that it has persisted for years.

Not only is it annoying, this particular product flaw makes development of simulations that require data entry, cumbersome and time consuming. None of the "customer based solutions" (while appreciated) have worked for me...and I have tried them all.

I find it quite unacceptable that Articulate has not addressed this issue; I sincerely hope it is resolved soon.

I couldn't agree more, with every statement, if you paid me. 

Rory Lavender

Me too. This could very well have been a deal-breaker for us concerning Storyline if I had thought to check the forums before purchase. As I have said before, most of our e-learning is computer simulations. The constant reverting back to Arial 15.5 when a text box is selected is unacceptable.

Ashley Terwilliger

Hi Bryan,

Sorry you're running into this issue and we have reported it to our team. It took some time to narrow down the specific issues here, and I apologize for that - but now that we've got them clearly detailed and reported to our QA team it's in their hands for further investigation. Once we have any additional updates or information to share, we'll be certain to do so here. Anyone who is subscribed to the thread either by responding or using the "subscribe" button at the top will receive those updates automatically. 

Conor Twomey

I was getting ready to log a new ticket the other day on this with Articulate; I was creating a story depicting what was wrong. I had generated a try me of a simulation I was working on that had a lot of user entry fields. I had already replaced all the user entry fields with new created TEXT ENTRY FIELDS that operated correctly except for the big issue of not being the default position for the cursor when the user got to the screen instead they had to click on it.  

So I copied one of the slides that I had engineered to appear correct to the user into a new story; then I copied and pasted into the same new story the same slide pre-engineering to illustrate to Articulate how it was not working correctly. I then went into preview to verify that everything looked correct…. and OMG the un-engineered slide was working correctly…… when I transitioned to that slide the cursor was defaulted in the text entry field and when I typed in the text it was not too big and it was not wrapping out of sight.

I was gobsmacked (for you yanks that’s astonished). I copied all of the slides from the original unedited try me story into the new story and they all worked correctly when I previewed it.

So now whenever I create a new try me simulation I copy it into a my new seed version (see attached) that works and then save it as a new story that has the correct functionality.

It has only been a few days but so far everything is working correctly.