Forum Discussion

BetsyFuller's avatar
BetsyFuller
Community Member
24 days ago

Screen Recording Try Mode: Can you turn off button hover states in the captured screens?

Hi Everyone!

I'm currently trying to create some Screen Recording - Try Me mode activities for learners to practice using a software application. The challenge I'm running into is that each of my screens has "called out" the spots where learners should click next (shown objects, like a button, in a hover state so it stands out). For example, the step may be "Click the Save button." To complete this step, I want the learner to locate the Save button on their own and click it. However, the screen recording feature has actually shown the Save button in a hover state already, meaning you can tell that's the Save button they should be clicking.

Is there a way to have buttons remain in their normal state, so it's a bit more challenging for learners to complete each action?

Any thoughts on / help with this would be amazing! Thanks!

2 Replies

  • Hi BetsyFuller​,

    Great to see that Ron has been helping you.

    Currently, Storyline doesn’t have a built-in setting to suppress hover states during 'Try Mode' screen recordings. When you record a screen in Storyline, it captures the cursor movement and the UI state at the moment of interaction. That behavior is baked into the recording from the time it was captured and can't be toggled off later.

    Action Fine Tuning is helpful for trimming the timeline of a recording. Such as adjusting the start and end frames for a specific step. However, it cannot modify what's inside a frame, only which frames are used. There may be edge cases where AFT can help if the hover state appears briefly before the actual click. If that's the case for your recording, you can try trimming the start frame to an earlier/later moment where the button is still in its normal state.

    Having said that, I can see the value in a feature that gives authors more editing control over the playback UI of screen recordings. I've submitted this as a feature request on your behalf, and we'll let you know if we release a future update that helps!