When converting a Storyline file to Storyline 2, all our previously developed eLearning courses Next buttons on interactive slides have larger font than what was specified in the Storyline file. Has anyone else experienced this? What can be done in Storyline to help the text maintain the correct font size when being upgraded to Storyline 2?
Storyline 2 handles text a bit differently than Storyline 1, and you'll see information here on an issue with adding an additional pixel to the right margin. It looks like you may be running into that issue. If it's an actual font size change (hard to tell from just images alone) could we take a look at one of your sample .story files in SL1?
Thanks Anita - I just took a look and upgraded it - and the next button stayed at 10 pt. I did see the change as I mentioned associated with the pixel. Please also confirm you're working on project files as described here to prevent odd behavior.
Just checking that you received my reply via email around 4:30 on Friday 12/19/2014.
"Thank you for taking the time to review the file and see if you could duplicate the error. Initially it doesn't appear that the NEXT button has any differences from SL1 when upgrading to SL2, but when you look at an interactive slide where we've built it in states, that's where the issue occurs. I've screen recorded more detail if this is helpful, and include time stamps below.
00:15 Opening the file in SL1 01:01 Copying the file for upgrade to SL2 01:29 Upgrading the file to SL2 01:46 SL1 interactive slide with NEXT button states (normal) 02:19 SL2 interactive slide with NEXT button states (text is too large) 02:45 SL1 SCORM in live environment - all buttons appear normal 03:06 SL2 SCORM in test environment - all NEXT buttons with states have incorrect font size
I greatly appreciate any information you can provide on why the text in states is not staying the same as all text when upgrading from SL1 to SL2.
I checked your case and the email did come through. Ashley is out of the office today, but I am sure she will respond to your email shortly after she returns :)
I just replied to your case, but also wanted to post my reply here:
Thanks for the video showing the difference. I see what you're referring to, and last week when I tested this I didn't see a change in the font size (I also should have taken a video) but just the addition of the extra pixel. I tested your file again, by upgrading it and I see the change in font size. I'm trying to replicate this in my own files, by creating buttons or shapes and then adjusting the states for those - and I'm not able to do so. When I tried to copy your button into my own Storyline file to see if it was specific to how you set up your button - it didn't appear within Storyline (although I could see it on the timeline) which makes me wonder if there is some element of corruption associated with the button that could be contributing to this behavior.
f so, please walk me through the steps you took to set that button up as I can see it's a png image that you've also applied states too and share the SL1 file here with me.
11 Replies
Hi Anita,
Storyline 2 handles text a bit differently than Storyline 1, and you'll see information here on an issue with adding an additional pixel to the right margin. It looks like you may be running into that issue. If it's an actual font size change (hard to tell from just images alone) could we take a look at one of your sample .story files in SL1?
Ashley, thank you for your quick reply! The text is adjusted up from 10 points in the saved .story file to 13.5 when it is upgraded to Storyline 2.
Thanks for confirming Anita - do you have a sample SL1 file you could share here with us?
Would it be possible to email you a link to the file in our Dropbox? It's not a file I can share with the public.
Thank you,
Anita
Hi Anita,
Sure you can upload the file or the dropbox link to me here privately.
Thank you, Ashley. I've used the contact form to send the file. Looking forward to any direction you can provide.
Thanks Anita - I just took a look and upgraded it - and the next button stayed at 10 pt. I did see the change as I mentioned associated with the pixel. Please also confirm you're working on project files as described here to prevent odd behavior.
Just checking that you received my reply via email around 4:30 on Friday 12/19/2014.
"Thank you for taking the time to review the file and see if you could duplicate the error. Initially it doesn't appear that the NEXT button has any differences from SL1 when upgrading to SL2, but when you look at an interactive slide where we've built it in states, that's where the issue occurs. I've screen recorded more detail if this is helpful, and include time stamps below.
00:15 Opening the file in SL1
01:01 Copying the file for upgrade to SL2
01:29 Upgrading the file to SL2
01:46 SL1 interactive slide with NEXT button states (normal)
02:19 SL2 interactive slide with NEXT button states (text is too large)
02:45 SL1 SCORM in live environment - all buttons appear normal
03:06 SL2 SCORM in test environment - all NEXT buttons with states have incorrect font size
I greatly appreciate any information you can provide on why the text in states is not staying the same as all text when upgrading from SL1 to SL2.
"
Hello Anita!
I checked your case and the email did come through. Ashley is out of the office today, but I am sure she will respond to your email shortly after she returns :)
Thank you!
Hi Anita,
I just replied to your case, but also wanted to post my reply here:
Thanks for the video showing the difference. I see what you're referring to, and last week when I tested this I didn't see a change in the font size (I also should have taken a video) but just the addition of the extra pixel. I tested your file again, by upgrading it and I see the change in font size. I'm trying to replicate this in my own files, by creating buttons or shapes and then adjusting the states for those - and I'm not able to do so. When I tried to copy your button into my own Storyline file to see if it was specific to how you set up your button - it didn't appear within Storyline (although I could see it on the timeline) which makes me wonder if there is some element of corruption associated with the button that could be contributing to this behavior.
Could you create a new version of that button in a new SL1 file, and then upgrade it to SL2 to let me know if the behavior persists? You'll want to confirm that you're working locally and following along with all the other guidelines mentioned here: https://www.articulate.com/support/storyline-2/create-edit-and-publish-articulate-storyline-courses-on-your-local-hard-drive
f so, please walk me through the steps you took to set that button up as I can see it's a png image that you've also applied states too and share the SL1 file here with me.
This discussion is closed. You can start a new discussion or contact Articulate Support.