In certain situations the zoom button will not enlarge the photos. They will stay the same or sometimes even get smaller. Has anyone found a fix for this? It seems to have something to do with where the photo is located on the slide (too close to the edge).
Can you tell us where this happens, please? Are you seeing this when previewing or after publishing?
Also, which version of Storyline are you currently using to develop your project? You can find this by clicking Help >> About Storyline.
The latest version for Storyline is Update 5. Articulate Storyline Update 5 includes bug fixes, performance improvements, and HTML5 output enhancements. Click here for details.
If you could share a little more about when this happens for you, we can try to get this working properly for you.
This happensboth in preview mode and when it is published to our LMS. I have tried to swapthe picture out with one that has previously worked, but that didn’t change theproblem. I am wondering if it is something that deals with the picture’slocation on the slide?
I am runningupdate 5.
My company andI are also are bothered by the fact that the zoom function is provennot to work on tablets. We have MANY courses where we have used this functionso as not to add more layers and make the course file sizes larger. Our coursesare designed to be taken in the field on tablets and mobile devices. Can youplease advise us on how close you are to a fix on this bug?
Are you able to share a .story file for the project where this is happening, please? It would be much easier to test the project on our end to see what's happening and confirm whether or not this is an issue we need to test with our Quality Assurance team.
Before you share the file, it really does sound like strange behavior.
I'd first recommend checking to ensure that you're working locally (since this happens when you preview as well as after publish):
Work on your local drive (your C: drive). Working on a network drive or a USB drive can cause erratic behavior, including file corruption, loss of audio, and other unexpected behavior.
You should also make sure the directory path to your project files and your published output is less than 260 characters (for example C:\Articulate).
Avoid using special characters, accents or symbols in your file names (this includes spaces and underscores).
Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.
If you're already working locally with your Storyline project files and you've updated, it may help to run a quick repair:
It may also be a case of corruption with the file itself. If that's the case, it may help to import the original content into a new, blank Storyline file:
3 Replies
Hi Sandra,
Can you tell us where this happens, please? Are you seeing this when previewing or after publishing?
Also, which version of Storyline are you currently using to develop your project? You can find this by clicking Help >> About Storyline.
The latest version for Storyline is Update 5. Articulate Storyline Update 5 includes bug fixes, performance improvements, and HTML5 output enhancements. Click here for details.
If you could share a little more about when this happens for you, we can try to get this working properly for you.
Thanks!
This happensboth in preview mode and when it is published to our LMS. I have tried to swapthe picture out with one that has previously worked, but that didn’t change theproblem. I am wondering if it is something that deals with the picture’slocation on the slide?
I am runningupdate 5.
My company andI are also are bothered by the fact that the zoom function is provennot to work on tablets. We have MANY courses where we have used this functionso as not to add more layers and make the course file sizes larger. Our coursesare designed to be taken in the field on tablets and mobile devices. Can youplease advise us on how close you are to a fix on this bug?
Hi Sandra,
Thanks for getting back to me!
Are you able to share a .story file for the project where this is happening, please? It would be much easier to test the project on our end to see what's happening and confirm whether or not this is an issue we need to test with our Quality Assurance team.
Before you share the file, it really does sound like strange behavior.
I'd first recommend checking to ensure that you're working locally (since this happens when you preview as well as after publish):
Additional information regarding "Naming Files, Paths, and Namespaces" in Windows operating systems can be found in the following Microsoft article.
If you're already working locally with your Storyline project files and you've updated, it may help to run a quick repair:
Articulate Support - How to Repair Articulate Storyline
It may also be a case of corruption with the file itself. If that's the case, it may help to import the original content into a new, blank Storyline file:
Importing from Another Storyline Project - E-Learning Heroes
If you've tried all of this and it's still not functioning properly, please attach the .story file for the project here, so we can take a look.
Best,
Christine
This discussion is closed. You can start a new discussion or contact Articulate Support.