29 Replies
Christine Hendrickson

Hi Wendy,

Sorry for the confusion, I was thinking about the definition, not the terms. I see exactly what you mean, now, and I ended up with the same result using the term you provided. It looks like this is by design, however, most long terms get cut off with the "..." at the end. I think allowing an extension of the term pane, or wrapping the term titles would make an excellent feature request, though. I can certainly see how this would be something you'd like to have when the terms are quite long!

Tali Bromberg

Hi Christine,

I have a similar issue, only in my case it is the definition, and not the term, that appears cut off.

When you click a term, you see only the first few lines of the definition and then the rest is cut off. This only happens with some of the terms, not all of them.

When you double-click the term, however, you do see the definition in its entirety. Although double clicking solves the problem, I still prefer my learners to be able to view the entire definition without having to double click.

In case it makes any difference, my definitions are written in Hebrew.

Is there a way to fix this?

Thanks,

Tali

Christine Hendrickson

Good morning Tali!

That does sound strange. If the definition is long, it should scroll the pane that displays the content when only clicked once. Just curious, how are you viewing the course when the definitions are cut off? Does this happen when previewing, or after you've published? 

If this is happening after you've published and uploaded the course to an LMS or web server, try clearing your browser cache.

If this is happening when previewing your course, please make sure your machine is currently set to 96 DPI. Storyline doesn't currently support 120 DPI. If your system is set to 120 DPI, you may experience erratic behavior, such as:

*  Elements of the application are misplaced or distorted.

*  Objects are misplaced or distorted when previewed or published.

*  Zoomed images don't work as expected.

*  Font sizes are incorrect after using the translation features.

Here's how you can switch to 96 DPI

You may also want to make sure you're running the most recent version of Storyline. To find your current version, please click on "Help" and "About Articulate Storyline". If you're not running version 2 (1212.1412), please download and install Update 2 from the link below:

Articulate Storyline > Download Update 2

Let me know how it goes!

Thanks,

Christine

Tali Bromberg

Hi Christine,

Thank you for your detailed reply! My display is set to 100%, and I am using the latest version of SL (1212.1412).

I was trying to isolate the problem and I think it might be caused by changing the player properties to "Text is read from: Right to Left".

Please have a look at the attached example.

Any ideas?

Thanks,

Tali

Christine Hendrickson

Good morning Tali,

Thanks for the file! I took a look and I see the same thing. 

I've done a little testing on my end and I agree, it does look like this happens only went the direction of text is changed. If I use "Left to Right", everything seems to show up properly. 

I haven't been able to find a bug report for this specific issue, so we may want to pass this information on to our support team. If they're unable to find a solution, they'll be able to pass the file on to our QA team for testing. 

Please go ahead and submit a support case with us, including your file. You'll be able to attach the .STORY file on the second page of the following form:

Articulate Support - Submit a Support Case

Please be sure to include a description of your issue. Please also include the URL for this thread in the form. Also, please share the case number with me. You're welcome to do so here, or in a private message. This way I can follow the progress of the case and update this thread.

I'll continue testing on my end, as well. If you happen to find any other information, please share :)

Thanks!

Deb Peak

So, it's 2 years later--was this feature ever added? I'm in Studio 13 and I still have the same problem--and we have lots of long terms/acronyms that learners are forever complaining about not being able to see the whole term, and it wastes lots of space to spell them out again in the definition. The Outline wraps long slide titles, why doesn' the Glossary do the same?

Brandon Dameshek

So has this feature still not been "updated"? Sorry, but it's somewhat useless as is. That is, not being able to wrap the text in the definition window so as to see the term that's being defined makes little sense. I would essentially have to include the word/term that's being defined in the definition, which is essentially redundant. Has anyone figured out an alternative? Thanks for your help.

Leslie McKerchie

Oh, sorry about that Brandon. Storyline forum, so could have been my error in assumption.

Unfortunately, I have no update to provide here either, but I do know that many users have found that utilizing a smaller/narrow font helps:

Click on "Interaction Properties" and select the "Colors and Effects" tab. In the "Interaction Fonts" section, you can change the fonts uses for both the title and slide content.

 

Brandon Dameshek

Hey, Leslie:

Duh. Totally forgot I was on a Storyline thread, so the apologies are mine.

As far as your suggestion, though, it's not going to work. (I actually tried it already.) Some of my terms/acronyms are really long, so I don't think there's a font that will solve the issue. So, at this point, I guess there's still no way to wrap the text?

Brandon Dameshek

Hey, Janelle:

Unfortunately, no. I had to publish my course with my glossary terms looking just like yours, which was unbelievably frustrating. As far as I know, Articulate has not updated this feature. As always, I'm sure they will suggest that you submit this as a features request.

Good luck!

Eric Casolo

I'm having an issue with cut off as well. I changed "notes" to "cc" and added script text from the storyboard. I'm getting cut off text on the right almost like there is a white bar all the way down the right side.

I published this locally, on a web server and also thru cloud scorm.

Any ideas on why this would be happening?

 

Thanks, E