I made a menu structure with 4 buttons, each button represents a chapters. At the beginning only chapter 1 is accessibble, the other 3 chapters have the Disabled state as initial state.
The problem is when I hover over chapter 1 the Hover effect isn't showed correctly when the mouse first was hovered over chapter 2, 3 of 4 which have the disabled state. The hover effect only works correctly when chapter 1 is hovered over from another place of the screen. I can't figure out what causes this. I attached an example.
The same issue occurs when I look at your file. That is very weird behavior. I also tested what would happen if I changed the 2nd button to normal (instead of disabled). Its hover state also didn't appear when I first approached it after crossing over the disabled buttons. However, it I kept moving my mouse around, the hover states for both buttons 1 and 2 did appear!
In any case, this behavior shouldn't happen. But I don't think the forum can help. I suggest that you submit a case to the Articulate team, so they can investigate what the problem is.
I checked this as well, interesting behavior. Saw something similar with another forum user I was helping the other day, rolling over other buttons caused the initial button not to show rollover state.
I was thinking it was due to the shadow effect on the button, when removed seemed to help, but not here.
NOTE for Articulate: One thing I do notice. If you rollover button 1 in the upper-left corner, (Where the clock icon is) the rollover state does come back. I am not sure why the upper-left. I notice this exact same behavior the other day on a similar case in this forum. I thought maybe it was the way the buttons was initially made.
Hope that helps to get to the bottom of the issue. ;0)
Thanks for reaching out. I'm sorry that you ran into a hover state on an object not working when you mouse over another object with a disabled state. We have reported it to our team, and continue to keep an eye on it to evaluate how many customers are impacted and what impact it has on courses.
I'm sorry that I can't say if this issue will be fixed soon, but you're in the right place to stay updated on this bug's progress.
I'm excited to return to this discussion with exciting news! We just released Storyline 360 (Build 3.55.25954.0), which includes the fix for the bug where sometimes a hover state wouldn't appear when there were disabled objects on the same slide, and sometimes text shifted when hovering over an object in a course using the classic player.
To take advantage of the newest release, make sure to update Storyline 360 in your Articulate 360 desktop app!
Please don't hesitate to reach out to us if you run into any issues updating or have additional questions. You can reach us in this discussion or by submitting a support case!
I am now getting the opposite issue. I have a button with Normal, Hover and Disabled states. When a Variable is set to true in the course the button becomes Disabled...which it does, but the Hover state still works, as in both Disabled and Hover shows. I do not want the Hover to work once the Disabled State is activated. Thought that was the purpose of Disabled.
Insert a new shape (triangle works for me, as I'm trying to create a "Play" button and the Play icons all use donuts as the ring). Give it 3 states: Normal, Disabled, Hover. Put a glow on Hover; gray out the Disabled; different color for Normal. Set the Initial State to "Disabled." Insert a circle behind the triangle, duplicate the states and the Initial State.
Put a Cure Point on the timeline, and a trigger which changes the state of the two objects to "Normal" when the timeline reaches the cue point. Preview the slide. Notice the state of the objects remains disabled when you hover over the image before the play head reaches the cue point.
Group the 2 objects together and repeat the preview of the slide. Now, the Hover state will be triggered at any point.
Thank you for providing these steps! We have this already logged as a software bug where the Hover state is active on a grouped object in the Disabled state. I've linked this discussion to our bug report so that I can circle back when we have an update.
I appreciate the time you took to explain these steps!
Hello, Lauren, I am experiencing the bug you described: The hover state is active on an object in a group even though the object is disabled. Has there been a fix to this issue or is the only solution to ungroup object? Thank you for your help.
I guess the best thing you can do is to create a trigger "Change state of object to Disabled When the user hovers over Group". I don't see this behaviour has been fixed.
14 Replies
Hi, Stijn,
The same issue occurs when I look at your file. That is very weird behavior. I also tested what would happen if I changed the 2nd button to normal (instead of disabled). Its hover state also didn't appear when I first approached it after crossing over the disabled buttons. However, it I kept moving my mouse around, the hover states for both buttons 1 and 2 did appear!
In any case, this behavior shouldn't happen. But I don't think the forum can help. I suggest that you submit a case to the Articulate team, so they can investigate what the problem is.
https://articulate.com/support/contact/case
I checked this as well, interesting behavior. Saw something similar with another forum user I was helping the other day, rolling over other buttons caused the initial button not to show rollover state.
I was thinking it was due to the shadow effect on the button, when removed seemed to help, but not here.
NOTE for Articulate: One thing I do notice. If you rollover button 1 in the upper-left corner, (Where the clock icon is) the rollover state does come back. I am not sure why the upper-left. I notice this exact same behavior the other day on a similar case in this forum. I thought maybe it was the way the buttons was initially made.
Hope that helps to get to the bottom of the issue. ;0)
Hi Everyone,
Thanks for reaching out. I'm sorry that you ran into a hover state on an object not working when you mouse over another object with a disabled state. We have reported it to our team, and continue to keep an eye on it to evaluate how many customers are impacted and what impact it has on courses.
I'm sorry that I can't say if this issue will be fixed soon, but you're in the right place to stay updated on this bug's progress.
This post was removed by the author
Hi Ren,
Thanks. Do I still need to submit a case to the Articulate team or is this not necessary?
Not necessary, Stijn. I appreciate your willingness to help us out :)
Having the same issue!
Hi all!
I'm excited to return to this discussion with exciting news! We just released Storyline 360 (Build 3.55.25954.0), which includes the fix for the bug where sometimes a hover state wouldn't appear when there were disabled objects on the same slide, and sometimes text shifted when hovering over an object in a course using the classic player.
To take advantage of the newest release, make sure to update Storyline 360 in your Articulate 360 desktop app!
Please don't hesitate to reach out to us if you run into any issues updating or have additional questions. You can reach us in this discussion or by submitting a support case!
Stay well!
I am now getting the opposite issue. I have a button with Normal, Hover and Disabled states. When a Variable is set to true in the course the button becomes Disabled...which it does, but the Hover state still works, as in both Disabled and Hover shows. I do not want the Hover to work once the Disabled State is activated. Thought that was the purpose of Disabled.
I'm sorry to hear that, Darren! For your trigger, are you changing the state of the button when the timeline starts or when the variable changes?
Here's a quick tutorial where I've explained my steps in trying to recreate this issue.
Insert a new shape (triangle works for me, as I'm trying to create a "Play" button and the Play icons all use donuts as the ring). Give it 3 states: Normal, Disabled, Hover. Put a glow on Hover; gray out the Disabled; different color for Normal. Set the Initial State to "Disabled." Insert a circle behind the triangle, duplicate the states and the Initial State.
Put a Cure Point on the timeline, and a trigger which changes the state of the two objects to "Normal" when the timeline reaches the cue point. Preview the slide. Notice the state of the objects remains disabled when you hover over the image before the play head reaches the cue point.
Group the 2 objects together and repeat the preview of the slide. Now, the Hover state will be triggered at any point.
Hello Joseph!
Thank you for providing these steps! We have this already logged as a software bug where the Hover state is active on a grouped object in the Disabled state. I've linked this discussion to our bug report so that I can circle back when we have an update.
I appreciate the time you took to explain these steps!
Hello, Lauren, I am experiencing the bug you described: The hover state is active on an object in a group even though the object is disabled. Has there been a fix to this issue or is the only solution to ungroup object? Thank you for your help.
I guess the best thing you can do is to create a trigger "Change state of object to Disabled When the user hovers over Group". I don't see this behaviour has been fixed.
Hello Kimberly and Nedim,
We do not have any updates at this time. I've added your voices to this bug report, and we will update this discussion with any news in the future.
Have a great start to your week! ✨