cut'n'paste of hyperlinks and mouse-over states

Jan 06, 2017

How do I file a bug against the product, and how can I leave a feature request?

I'll pretend this post is about getting an answer to these questions, but really, its about letting me vent some steam...

 

... at 1am last night I discovered i had wasted 2 hours work.  I had two layers, the first called "required" the second called "optional". I created a list of many dozen URL links in the first layer, and then cut'n'paste' the text box contents to the second box.  Then i deleted half the contents from each layer depending on whether the content was required or optional.  An easy, efficient way of generating the lists I needed.  Then I repeated this process for 7 more categories and previewed the project and saw that half the URL links were not working.

What happened?  Well, cut'n'paste of a link creates new text that "looks like" a link, and I assumed therefore it was a link.  I see now that the triggers did not copy over.  I suppose I can understand why a trigger might not copy but in that case, the copied text should NOT be formatted to suggest it is really a link.  The blue underline thing is universal in meaning "hyperlink" and it was hugely frustrating to find that Storyline regarded my copied links as regular text while still formatting it as a link.   I need to now recreate a HUGE number hyperlinks just because cut'n'paste didn't keep the hyperlink.  I would argue this is a bug, but perhaps its a feature request.

 

I also noticed that a mouse-over trigger to change the state of a text box (with "restore on mouse leave" set) works for story.html but not for story_html5. In the latter case, when the mouse moves away, the text box shows the default and mouse over states simultaneously.

 

2 Replies
Ashley Terwilliger-Pollard

Hi Gavin,

I totally understand the need to vent, especially when this caused you some extra work and headaches. Let's get you back to working well by figuring out the problems you mentioned here and hopefully that'll help in the future. 

First, what version and update of Storyline are you using? I want to look at replicating it in the same environment to be sure I'm clear on your steps and then we can go from there for bug vs. feature, or maybe another idea for the way to do what you want! For reference, we're on Storyline 1 Update 10, Storyline 2 Update 11 and Storyline 360 Update 3. The easiest way to check is to open Storyline and find the Help tab, click on About Articulate Storyline and you'll see the version and update number listed there.  If you're not on the latest update of any of those, you can use the "Check for updates" to download and install the latest update.

For the issue with the mouse over and hover, are you using the built in hover state and have you added any additional triggers to control the state from normal -> hover? If you've added additional triggers to built in states that can cause some odd behavior as Storyline is trying to make them behave as they were coded (described here for Storyline 2, but the same definitions across the board). 

Also, when you're testing the HTML5 output, what browser/device are you doing so in? This will also connect back to the version of Storyline  you're using as we've got broader HTML5 support the newer Storyline versions. 

Lastly, you can always submit Support cases here and our team will be able to work with you one on one to determine if it's a bug, expected, or any other ideas/solutions for your issue. Feature requests can also go here to our Product team

If you want to go right ahead and work with our Support Engineers on this, feel free to use that link above - and if you want to give me a heads up I can follow along as well. Otherwise we can keep it going here in the forums with answers to the queries above. 

Gavin Nesom

thanks for the reply, and sorry for a tardy response.

I am using Storyline 2 update 11.

For the mouse-over/hover issue, I did not have any additional triggers.  The html5 output showed the defaul and hoverover text for IE 11, Firefox 50.1.0, and Chrome 55.0.2883.87 m

The link issue is easy to replicate.  Create 2 or more links, copy and paste to another location (i was copy'n'pasting between text boxes in a scrolling panel).  the copied location will have the appearance of links, but select just one of the links and edit it, and suddenly the formatting of all the copied text will change to reflect that they are not in fact links to a URL.  Because I did not edit the links, the copied text remained blue underlined so I incorrectly believed that the URLs were also copied over.

This discussion is closed. You can start a new discussion or contact Articulate Support.