I have not found any articles touching on this issue so I have created a new one:
We have underlined words in text blocks set to be animated with the "wipe" animation (from the left; by paragraph..? manually translated as we are using the german version; screenshot and zipped version of the published "Internet"-choice attached, as I cannot attach the .story file) and the visual effect is as follows:
The normal text lines are wiped onto the screen as usual but underlined text lines first wipe in the line of the underlined words, then the entire corresponding line pops in.
We are using the underlined words to show which ones are linked to lightboxes with the translations.
Sorry to hear you've run into erratic behavior with underlined text and the wipe transition feature in Storyline!
Just to clarify, are you using Storyline 3 or Storyline 360? Our development team is currently tracking a known bug where The underline appears first if wipe animation by paragraph is applied to text with underline.
To confirm if this is related to the issue you're seeing, it'd be helpful to have a closer look at your project file. If the .story file contains sensitive information, you can share it privately through a support case. We'll delete it from our system as soon as troubleshooting is complete!
In the meantime, my colleague Tom shared a workaround in this related discussion that you may find useful.
1 Reply
Hi Gregor!
Sorry to hear you've run into erratic behavior with underlined text and the wipe transition feature in Storyline!
Just to clarify, are you using Storyline 3 or Storyline 360? Our development team is currently tracking a known bug where The underline appears first if wipe animation by paragraph is applied to text with underline.
To confirm if this is related to the issue you're seeing, it'd be helpful to have a closer look at your project file. If the .story file contains sensitive information, you can share it privately through a support case. We'll delete it from our system as soon as troubleshooting is complete!
In the meantime, my colleague Tom shared a workaround in this related discussion that you may find useful.