51 Replies
Bruce Graham

Agreed.

There comes a point where, I think, one needs to ask the question "Is it more sensible to devise a coding-based solution/workaround, or does it make sense to have this as a standard option in some way?"

Like the "...commas in long numeric variables" solution, a number of elegant ways to do it, but surely it would be more helpful to IDs if the product just had it as standard now?

Bruce

Sasha Scott

I don't think the flashing button per se is important, however I would point out to the feature request people that:

- if each state had a timeline that could be looped (or not) that would be cool. Kind of like a button in Flash (which is what people are used to seeing/using)

In just the same way as Jeanette has pointed out there's a neat (unsupported?) trick to loop a layer, why not also a trick to loop a state?

It could be used for a lot of much cooler things than flashing buttons But in all seriousness, it would be more tidy than having to use a layer

Jerson  Campos

I don't know about how often this is asked  about, but I'm not a fan of blinking images either. I'll use this animation only when appropriate and as little as possible. I'm surprised it isn't an built in effect that can be applied.

For now, I think the best solution (and easiest) solution is to make the image blink itself, either through flash animation or an animated gif. I like using variables, but adding too many for a simple animation is just not worth it.

Bruce Graham

Just had a (major multinational) client ask for flashing "Next" button (I am using the built-in functions), "...as it is not obvious when to move to the next slide".

Could we perhaps request an additional enhancement to the flipping Seekbar, so that it gradually turns from green to red, and then sounds a small alarm/explosion noise SO THAT LEARNERS KNOW WHEN TO CLICK ON "NEXT".....

Sheesh....

Anyway - would still love to have a built in "pulse" state

Bruce

Rebecca Fleisch Cordeiro

Howdy,

Just now seeing this - and also that people are unsubscribing but still, thought I'd add my 2 cents.

I do have a non-flashing solution to subtly remind Learners about the built-in next button that takes little time, since it can go on the Master slide. I described it in a separate thread and have created a Screenr here:

https://player.vimeo.com/video/149070020

I know there are opposing opinions on blinking and flashing, but I definitely am in the "strongly dislike" camp.

Definitely the need for a prompt, as Melissa T. said, is dependent on course design and audience needs.

Interested in a built-in option as well, but hope it's not limited to blinking and flashing!

Bruce Graham

It is very easy for use to get caught up in our own knowledge-set.

A flashing Next button is something that users request, especially early on in their eLearning journeys - it's not always as obvious to them.

Think of it like the people who wander round an art gallery spending 30 seconds in a room, while someone may spend 30 minutes looking at one picture - they are the expert that knows what to look for.

The "normal" guys may occasionally need some help.

Just my 2p worth.

Bruce

Jerson  Campos

I'm also on the dislike camp about flashing or blinking anything. 1-2 blinks is fine to highlight are get attention, but a constant flash or blink is too much. For the "next" button, I will always include a grayed out  or "disabled" next button on every slide. When there needs to be a next button, It is usually a color that will stand out and draw a little attention. 

I've also recently seen a course that had a small area where text be displayed letting the user know when to click next to move on to the next slide. It was very small and didn't distract from the overall design.

Rebecca Fleisch Cordeiro

Hi Jerson,

Yes, a greyed out button is good IF you use custom buttons. But not everyone wants to; thus my solution, which sounds similar to what you say you saw recently: "course that had a small area where text be displayed..."

And just a follow-up that ff course we all would do as our clients prefer, even if it's something we don't like.

tim lambert

Jeanette Brooks said:

Another way to do it is use a layer, like in the attached example. The layer contains the next button, with Fade In/Fade Out animations for its entrance and exit. A trigger causes the layer to reveal when the slide timeline ends. On the layer itself, 2 triggers cause the layer to hide and then reveal, to create the looping/flashing effect. The layer properties are set to "Reset to initial state" to allow the layer's timeline to refresh every time.



I know this is an old post, but I was looking for the same functionality and Jeanette, your example worked a treat when published for iPad and Flash, but as an HTML published course the page seemed to flicker or refresh for each loop. Is this a bug or a consequence of it being HTML5.

Many Thanks for your help.

Christine Hendrickson

Hi there Tim,

It may simply be an issue with HTML5 output. One thing that may help is to make sure you're running the most recent version of Storyline. To find this information, click on "Help" and "About Articulate Storyline".

If you're not running version 3 (1305.2012), please download and install the update using the link below:

Articulate - Storyline Update 3

Once you've finished installing the update, please republish and test your course on the iPad. Hopefully you'll see some improvements after updating, if you haven't done so already.

Thanks!

Kate Hoelscher

Bruce Graham said:

In the beta I asked for a built-in state called "Pulse", as I think it would be incredibly useful, but not sure if it will make it to a production release or not.

Bruce


This sure would be helpful!  I had to have flashing, so I created multiple copies of one image and moved them around the timeline for fractions of a second at a time.  Worked...but huge file and tons of time.  They were all on layers so I would hesitate to use another layer for this but hey....awesome idea for the right situation!