Forum Discussion
Text in radio button 'jumps out' on hover
Hi everybody,
Weird thing going on here: when I make a radiobutton, and if the linked text is in 2 lines, storyline sometimes (not everytime as you can see in the video: https://360.articulate.com/review/content/97612add-4a29-4a5f-8f31-96a0fd7dbc90/review) automatically gives different lay-outs to the other states, like Hover, Down, etc. See image in attachment. I didn't do anything in particular as I recall.
Very annoying, since this means I have to adjust every states seperately to align with the Normal state. Or is there any quick fix available?
How come this happens? And is there anything I can do about it to prevent it from happening again?
I copied the radiobuttons where is works well to 'fix' the tirth one, but helas, it changes the states automatically again. Is it the text that triggers it?! Any tip is welcome here!
Hi Pierre,
Thanks for your suggestions. I will have a look at them when the issue reappears.
I already noticed that indeed, when you tweak the text-box after the states are made (they are made by default in the radio button-text boxes so difficult to prevent this from happening!), that the new settings don't always carry on to the different states. It's a pickle though, because sometimes they do alter with the normal state (as they should!), other times they don't... Isn't this worth a bug report and hopefully solution from the developer team?
I will also look into the 'wrap text' setting for every state.
Kind regards & have a nice weekend!
I think it is a bug in the end-user-experience perspective, but I don't think it will fit Articulate's definition of a bug. They'll think of it as a "feature" that all variables of the text box get carried over. Part of the problem is a lack of clarity on what a "state" is. The object isn't a "master". You can edit the normal state and paste something into the state, and it does not copy over to all of the "child-but-not-children" states. The states behave more like groups with built-in triggers; but then Articulate hasn't committed to that UX either, as you can't access that group in the timeline. Articulate has done us the "favor" of treating states like groups when it comes to focus order; that is, not including the child-but-not-children objects (so frustrating).
So my understanding of the solution, in order:
1) Submit "another" feature request that grouped objects appear in the focus order
2) Then submit a feature request that states get a UI treatment that better parallels their UX behavior as groups.
3) Then submit "another" feature request that "set as default" actually applies the variables of the text box as well.
