I was never able to get bullet points to animate correctly in a text box in previous versions of Storyline so I've always created a separate text box for each bullet point. To mimic a powerpoint feature (first bullet point fades as next bullet point is displayed) I created a textbox state that simply changed the font color to grey when the next bullet point appears in the timeline
When I update a file all of the grey textbox states that I have created revert to a smaller textbox that totally screws up the formatting. The only way to correct it is to edit each textbox state to adjust the size of the faded state.
After some testing I found that the additional state that I had created was reverting back to the size of the textbox defined in the slide layout that I had used (most textbox sizes had been altered to accommodate the text that I had used)
Thanks so much for sharing your findings here. I'm sure other users will find this helpful if they encounter a similar issue! So are you saying the solution you found was to change the size of the defined textbox in the slide layout before updating the file?
Not really a great solution... I have about a dozen courses with an average of about 60 storyboards. I was hoping for a bug fix before I decide to upgrade to 360. This was never an issue when I moved from SL1 to 2
Sorry for any confusion and thanks for sharing a description of what you've had to do surrounding this behavior. I can barely remember back to Storyline 1, but I know the animation by paragraph was always a tricky one and then was drastically better in Storyline 2 (part of me feels like you couldn't do it in Storyline 1 at all...but that could be the impending holiday brain I've got!). In regards to how you've set it up though - are you only seeing this behavior when upgrading files from SL1 to SL2? Without seeing your file, something that comes to mind is that there was a shift in behavior for text boxes within SL2 where an additional pixel was added to the end to accommodate some changes in text overall that were implemented, so you'd see that shift when upgrading a file.
Have you been testing this in SL360 as well? If you've got a sample file handy with your described workaround we're always happy to take a look too and that's the best way to help us determine bug, design and an author generated behavior - so feel free to upload it here using the "add attachment" button at the bottom of the forum reply.
You can also always reach out to our Support Engineers here. We are all getting ready for a little holiday break (read: lots of eating pie) but we'll be back to full strength on Monday, just perhaps with a few more pounds. ;)
I think you are correct... after a bit more testing the projects that had problems with the update were indeed originally created in SL1, then updated to SL2, then to 360. So the workaround shouldn't be as daunting a task as I had originally thought since most of my projects have been created in SL2 and these seem to be updating correctly.
5 Replies
Hi Brian,
Thanks so much for sharing your findings here. I'm sure other users will find this helpful if they encounter a similar issue! So are you saying the solution you found was to change the size of the defined textbox in the slide layout before updating the file?
Hi Alyssa
Not really a great solution... I have about a dozen courses with an average of about 60 storyboards. I was hoping for a bug fix before I decide to upgrade to 360. This was never an issue when I moved from SL1 to 2
Hi Brian,
Sorry for any confusion and thanks for sharing a description of what you've had to do surrounding this behavior. I can barely remember back to Storyline 1, but I know the animation by paragraph was always a tricky one and then was drastically better in Storyline 2 (part of me feels like you couldn't do it in Storyline 1 at all...but that could be the impending holiday brain I've got!). In regards to how you've set it up though - are you only seeing this behavior when upgrading files from SL1 to SL2? Without seeing your file, something that comes to mind is that there was a shift in behavior for text boxes within SL2 where an additional pixel was added to the end to accommodate some changes in text overall that were implemented, so you'd see that shift when upgrading a file.
Have you been testing this in SL360 as well? If you've got a sample file handy with your described workaround we're always happy to take a look too and that's the best way to help us determine bug, design and an author generated behavior - so feel free to upload it here using the "add attachment" button at the bottom of the forum reply.
You can also always reach out to our Support Engineers here. We are all getting ready for a little holiday break (read: lots of eating pie) but we'll be back to full strength on Monday, just perhaps with a few more pounds. ;)
Hi Ashley
I think you are correct... after a bit more testing the projects that had problems with the update were indeed originally created in SL1, then updated to SL2, then to 360. So the workaround shouldn't be as daunting a task as I had originally thought since most of my projects have been created in SL2 and these seem to be updating correctly.
Happy to hear that Brian and feel free to keep us posted if you need anything else.
This discussion is closed. You can start a new discussion or contact Articulate Support.