Forum Discussion
Double glitch: font size and indentation
Both errors are probably the result of something in the master slide layout. The second may also be the effect of copy/paste artifacts that occasionally crop up in SL360.
To address the first problem (the weird indent), you need to work with the paragraph settings:
These work as they do in a word processing tool. What I had to do to eliminate the weird indent effect was to copy the text out, paste it in a text editor (not Word, but Notepad or Notepad++) to ensure that it had no strange carriage returns or anything, then copy and paste it back in to the story. If I recall correctly I just pasted it into an empty text box - either off the slide or on a different slide altogether. Then I brought that text box back to the slide where I needed it.
I have no specific answer about why it occurs, but it has happened to me, and that's how I fixed it.
The second issue, while annoying, can be resolved by simply changing the properties of the text box:
I would probably uncheck the "autofit" option and then set the font to the desired size. ("Autofit" would most likely shrink the text to fit the dimensions of the text box as it currently is.)
Again, no specific causes, but as a general practice - if I experience a couple of these types of issues I start running my text through the Notepad option to ensure that there's nothing "hidden" in text formatting that could cause headaches.
Good luck.
re: 1, paragraph "negative margin"
As JHauglie said, that's related to the paragraph spacing. The example you show is what's called a hanging indent. That's often used for bullets. For example, here's what the "stoplight" text on the Site Visit 1 slide looks like with a hanging indent:
re: 2, variable text appears smaller
That is weird. I tried some different settings, but it the variable text still appeared in the smaller font. I suggest you contact support directly: https://access.articulate.com/support/contact
In the meantime, I think it'd be simpler to just put the different pieces of text in separate states. Then use triggers to show the appropriate state when the timeline starts on the slide based on the value of the UserOrg variable.
and by the way...
The menu slide is way more complicated than it needs to be. Selected is a built-in state. Any object with a Selected state will automatically change to that state when it is clicked. And, if you put multiple objects that have a Selected state into a button set, clicking one will automatically deselect the others. So, for each button, you can get rid of all the "change the state" triggers.
Also, if you set the Slide Properties to Resume Saved State, whatever button was selected when the user left the slide will be Selected when they return. In other words, you don't need these triggers either:
For more info:
- Storyline 360: Working with Button Sets | Articulate - Community
- PRIMER: Take advantage of built-in states | Articulate - Community
- Storyline 360: Adjusting Slide Properties | Articulate - Community
Thanks so much! I wasn't aware of the Button Set feature.