If I create a different state of an object by adding a secondary component (Example: An image with words underneath) then change the default state to something other than Normal - it causes weird things to happen including sometimes no longer being clickable without using the timeline itself.
I recreated an example of this error in this example. Here the states become combined so that both the Normal and Hover states appear together.
Sometimes if you group the 2+ items in the state itself, it goes back to working normally - however here it doesn't.
Sorry to hear that you encountered this issue. I opened a case on your behalf so our support engineers can investigate the behavior. Someone from our team will be in touch shortly!
I feel like there is a certain condition that creates the bug because while we see evidence of its existence - we cannot guarantee that it appears because it manifests itself in several ways.
To me, that's a code hiccup somewhere. Either within Articulate, or in the browser itself.
Miles, this is working as intended. Well, maybe not as intended, but as expected.
The built-in states (those with named on the drop-down list) are overlays of the Normal state. That means they don't erase Normal, they just show over it. There are two simple solutions:
1. Use states with custom names. The drawback to that is that you have to write your own triggers to replace the built-in superpowers that the different states have. I did that with the textbox in the sample.
2. Mask the text from the Normal state. I did that in the sample by giving the textboxes in the Hover and Down states a white fill.
Having the picture start in Hover state means it stays in Hover until you hover over it, then leave it. If that's what you want, keep it, otherwise, you may want to change it.
Having groups in the states will most likely cause problems someplace down the line. Groups don't play nicely with states, triggers, objects, or anything else that can be on a SL slide. Pasting objects into a state makes them all act as one object, so you don't need groups. Take it from someone with lots of very unpleasant experiences - You will most likely be sorry if you use groups, but especially inside a state.
3 Replies
Hi Miles,
Sorry to hear that you encountered this issue. I opened a case on your behalf so our support engineers can investigate the behavior. Someone from our team will be in touch shortly!
I feel like there is a certain condition that creates the bug because while we see evidence of its existence - we cannot guarantee that it appears because it manifests itself in several ways.
To me, that's a code hiccup somewhere. Either within Articulate, or in the browser itself.
Thank you for looking into it Joe.
Miles, this is working as intended. Well, maybe not as intended, but as expected.
The built-in states (those with named on the drop-down list) are overlays of the Normal state. That means they don't erase Normal, they just show over it. There are two simple solutions:
1. Use states with custom names. The drawback to that is that you have to write your own triggers to replace the built-in superpowers that the different states have. I did that with the textbox in the sample.
2. Mask the text from the Normal state. I did that in the sample by giving the textboxes in the Hover and Down states a white fill.
Having the picture start in Hover state means it stays in Hover until you hover over it, then leave it. If that's what you want, keep it, otherwise, you may want to change it.
Having groups in the states will most likely cause problems someplace down the line. Groups don't play nicely with states, triggers, objects, or anything else that can be on a SL slide. Pasting objects into a state makes them all act as one object, so you don't need groups. Take it from someone with lots of very unpleasant experiences - You will most likely be sorry if you use groups, but especially inside a state.