I have buttons, using the built-in Visited state. The state happens to have a small float-up animation (not sure if that is relevant, but mentioning it here): 0.5-second animation of a little checkmark.
Click the button, a layer appears, then when you close the layer, the button should be in the visited state (no triggers, I am simply using the built-in visited state).
This works sometimes. Then it doesn't. The same file works for one person (as a published file on the web) and others not. Works for me sometimes, then not.
It will be because you are hiding the base layer objects, it works fine for me, suspect there is some confusion going on internally at times that prevents the sate change
Hi Phil - thank you for your reply and for reviewing the slide. Not sure what hiding the base layer objects has to do with it. The hiding occurs on the layer. The buttons are on the base. It seems like a glitch - either in SL or with my (old and slow) computer.
Although you don't see any triggers in the background, the course is using triggers to hide the objects. I try not to use it as it can upset states when they are returned when you close.
That is interesting. I always use that, hide base objects, for ADA issues when tabbing. If that is upsetting states on the base, that is a SL bug, if you ask me. Thank you again.
If you set the layer to prevent user from clicking on the baselayer then it will not allow the focus order below to be selected; also you then don't need to move the objects around in the focus order as the layer will have focus.
It is definitely a bug, the solution is not to hide the objects on the baselayer.
What it does mean is that your animation will then fire behind the layer rather than when the layer closes.
Have you reported this bug to Articulate? If I don't hide and disable the base layer, then the ADA user will be tab to the objects on the base layer.
I can add triggers: when the user clicks Continue (on a layer) change the state of button_X to visited. Obviously, this should happen automatically, but perhaps this extra "nudge" could fix the problem?
Hi Phil - Just wanted to follow up with you. I submitted a ticket for this issue and indeed it is a ("possible") bug and it is related to things you were saying. For now, if I simply remove the animation in the visited state of the buttons, the issue is avoided. Which is what I have done. Here is what tech support reported:
The change of state trigger is not working when the state has an object with animation if the following layer settings are enabled – Prevent the user from clicking on the base layer; Pause timeline of the base layer; or Hide objects on the base layer.
Thank you again for your feedback. Much appreciated.
9 Replies
It will be because you are hiding the base layer objects, it works fine for me, suspect there is some confusion going on internally at times that prevents the sate change
Hi Phil - thank you for your reply and for reviewing the slide. Not sure what hiding the base layer objects has to do with it. The hiding occurs on the layer. The buttons are on the base. It seems like a glitch - either in SL or with my (old and slow) computer.
Although you don't see any triggers in the background, the course is using triggers to hide the objects. I try not to use it as it can upset states when they are returned when you close.
That is interesting. I always use that, hide base objects, for ADA issues when tabbing. If that is upsetting states on the base, that is a SL bug, if you ask me. Thank you again.
If you set the layer to prevent user from clicking on the baselayer then it will not allow the focus order below to be selected; also you then don't need to move the objects around in the focus order as the layer will have focus.
It is definitely a bug, the solution is not to hide the objects on the baselayer.
What it does mean is that your animation will then fire behind the layer rather than when the layer closes.
Have you reported this bug to Articulate? If I don't hide and disable the base layer, then the ADA user will be tab to the objects on the base layer.
I can add triggers: when the user clicks Continue (on a layer) change the state of button_X to visited. Obviously, this should happen automatically, but perhaps this extra "nudge" could fix the problem?
I have probably reported at some point, I don't use hide option very much at all anyo=more so not really an issue for me.
If you set the layer to prevent user from clicking on the base layer the layer will take focus.
The trigger may help set automatic triggers using triggers can often cause issues.
Hi Phil - Just wanted to follow up with you. I submitted a ticket for this issue and indeed it is a ("possible") bug and it is related to things you were saying. For now, if I simply remove the animation in the visited state of the buttons, the issue is avoided. Which is what I have done. Here is what tech support reported:
The change of state trigger is not working when the state has an object with animation if the following layer settings are enabled – Prevent the user from clicking on the base layer; Pause timeline of the base layer; or Hide objects on the base layer.
Thank you again for your feedback. Much appreciated.
Hi Amy glad you got it fixed, thanks for the update.