Shape properties fill width not the same as displayed shape width

Hi Support,

I think there are a few bugs in Storyline 2, relating to shape fills.

My Master Slide dimensions are 1280 x 720 pixels.

I am inserting a few rectangle shapes into my Master Slide (see attachment 1.png). 

I would like the rectangle shapes to be exactly 1280 pixels in length so that they cover the entire width of the slide (also important for overlapping rectangles in other areas).

When I enter a width of 1280 pixels there is an extra pixel shown at the far right hand edge (see 2.png).

There are two bugs as far as i can see:

1.  Line Bordor justification displays from different points, depending on shape side (see 3.png).

2. In the shape properties I have set the line Color to "No line", however an extra pixel is still created at the right and bottom edge (see 2.png).  If i select no fill an extra pixel is not displayed so potentially the fill is drawn incorrectly and might be linked to point 1. 

We need to make the Master Slide quickly so that we can start making courses.  this problem is amplified by the more shapes that are used on slides.  Any solutions?  

Cheers.

Matt

 

5 Replies
Ashley Terwilliger-Pollard

Hi Matt,

Thanks for sharing the images here. I'm not seeing the same thing when I format the shape using the "size and position" settings to have it match the height and/or width of the overall slide size. Are you using the latest update of Storyline 2, update 7? Could you share the .story file with us so that we could take a look at your set up and anything specific that could be playing a role in this? 

Matthew Brannan

Hi Ashley,

Thanks for your reply.

I am using Storyboard version 7 (see 4.png).  I have attached my blank storyboard with the slide master attached (see MJB.story). 

I have looked into this a bit more and it looks like it affects the master slide and not subsequent master layouts (see 5.png vs 6.png).

Unfortunately this extra pixel sometimes appears in different slides i make, probably linked to the error in the Slide Master.  Hope that helps.

Matt

 

Ashley Terwilliger-Pollard

Thanks Matthew for sharing the files and the images. I opened your file, and didn't see the extra pixel on the slide master, the layout or even the slide itself. Here's an image of the slide master:  You mentioned it's appearing in the slides you make as well - but if it's off stage is that impacting your slide? I'd also be curious to have you confirm that you're working on files as described here, using the DPI setting of 96 and lastly if you could look at going through the repair. Those are all good steps for general odd/erratic behavior - as the file itself looks fine. 

Matthew Brannan

Hi Ashley,

Thanks for the reply.

I can confirm that I was working on the slides as described.  DPI setting = 96. 

I had a problem with my story where it said that it was locked.  I copied the story file and renamed it to something different and there is no longer a problem.  Must of been corrupted?

Thanks for your help.

Matt

 

Ashley Terwilliger-Pollard

No one likes that word (corruption) but it's always a tricky one to identify. You may want to keep in mind the following guidelines to prevent file corruption. 

1) Save and publish projects on your local hard drive. Working on a network drive or external USB drive can cause erratic behavior due to latency.
 
2) Save incrementally. If your app has an AutoRecovery feature, take advantage of it. If not, save a new version of your project every hour or so with a new file name each time. If a file becomes corrupt, you'll still have a working version available.
 
3) Install Dropbox. Snapshots of changes in your local Dropbox folder are kept for 30 days. If a file is damaged or deleted, you can restore a previous snapshot: https://www.dropbox.com/help/11/en.
 
4) Don't leave the app open and unattended for long periods of time. Some users have reported file corruption after leaving their apps open overnight. It's possible that a malware scan or disk backup could run because the machine is idle, making your app vulnerable to crashing.