11 Replies
Greg Schaffer

Thanks Parashuram. 

That solves one of my problems.  The other problem is when the text box position moves on me.  It doesn’t happen all the time, but is random.  For example, the text box position starts at horizontal 12 px, vertical 36 px and it will move down to vertical 45 px when I’m adding a photo to the slide. 

Bruce Graham

Greg Schaffer said:

Thanks Parashuram. 

That solves one of my problems.  The other problem is when the text box position moves on me.  It doesn’t happen all the time, but is random.  For example, the text box position starts at horizontal 12 px, vertical 36 px and it will move down to vertical 45 px when I’m adding a photo to the slide. 


I have started to experience that when inserting multiple videos and images. I had to publish today so no examples but does seem to happen regularly.

Ashley Terwilliger

Hi Greg, 

I haven't noticed it yet either, but as Jeff mentioned if you have a .story file you'd like to share with us you're welcome to send along here so that we can check it out. 

Also as a reminder, you'll want to follow these general guidelines to prevent odd behavior in Storyline:

Greg Schaffer

Thanks Ashley for the feedback on helping avoid odd behavior with storyline.  Working from my local C drive has helped keep the program from crashing on me. 

As for the issue of text box placement moving, I can’t duplicate the issue which made me think at first it was a user (me) error.  Thankfully it has only happened a few times with the last time being the only time I know I didn’t change anything on the slide.

Here is what happened.  I created the slide, previewed it and it looked good (by good, I mean the text box was placed where it should be placed).  I published the story, reviewed it online and it looked good.  I moved on to build other slides over the next few weeks.  During that time, the program was crashing on me.  When I reviewed the published version a month later, the text box on one of the slides had moved down.  It may have been due to file corruption, I don’t really know for sure. 

At this time, I’m starting over in terms of keeping track of when and why it happens.  Now that I’m saving the file only to my local C drive.

Ashley Terwilliger

Hi Greg,

File corruption can definitely be tricking to determine why it occurred, but keeping tracking of when you see the behavior and ensuring you always work on your local drive are both steps in helping us isolate what may have occurred. You mentioned viewing the published version a month later, and I assume it was a newly published version after you made the updates? Not the original version that you published? 

If you're able to replicate it again, please feel free to share the .story file with us here or share it privately with our Support team as Jeff mentioned. 

Ashley Terwilliger

Hi Greg, 

Working at anything other than 100% zoom is known to cause display issues while editing the text in comparison to how it'll be displayed once published. The other known display issue is working with a DPI setting other than 96, so you'll want to confirm that as well if you continue to experience the behavior.