I'm trying to set up a dial interaction. When you select the dial the arc shows, but when it's not selected, it is not visible. It is not visible when published either. In the design menu there is an option, Show Arc Always. I have turned this on, but my arc is still not visible. When i choose "when selected" the arc does not show. Any suggestions on how to make this work?
I am having the same issue as well (no arc in the published version. (I'm trying to create a version of the fave kids game Test Match - image is from published version)
Any idea why option to not have arc visible when published? This allows user to know how many graduations to expect instead of dialing blindly.
I'm guessing someone is going to respond - put that in as a feature request - but I've have had no luck for the past six years with any of my feature requests. Could be a case of Africa not being a significant player in this field or perhaps my feature requests have all been low on priority list of developers.
Thanks for letting us know what you'd like to see with the dial! The arc is there as a guide to show the rotation and steps when designing, but I appreciate you sharing that you'd like to have it published as well.
Ren, while I appreciate you responding - consider the following:
Maths and Science (Physics) users would like to use Articulate to produce high level maths and physics equations, such as we do when using Latex editor. Now, we not in the majority, so our requests falls on deaf ears when Articulate prioritises feature requests. End result, our requests never make it to the final implementation list. I know, I've been doing this for more than 6 years now with amazing unsuccess.
We get frustrated and opt to use other software more suited to our specific needs. And so maths and science users become even less in number and voting power when it comes to Articulate feature requests.
The point is, our numbers can never grow unless Articulate actually starts listening to our requests. We doomed to always be told: "What a great idea, why don't you submit that as a feature request."
9 Replies
Hi Renee
the arc only shows in the Editor not when published. Here is information from the KB about it
Show Arc
This determines whether the dial’s arc (pathway) is always visible in the Storyline editor or only when you select the dial object.
This property only affects a dial while you’re developing a project. The dial’s arc will always be invisible when you preview or publish.
I am having the same issue as well (no arc in the published version. (I'm trying to create a version of the fave kids game Test Match - image is from published version)
Hi Steve
did you see post reply above. The arc only shows in the editor not when published.
Hi Wendy,
That serves me right for working late. I read it "will always be visible". My apologies.
However, it's a pity that the arc is not visible in the published project.
Steve
Any idea why option to not have arc visible when published? This allows user to know how many graduations to expect instead of dialing blindly.
I'm guessing someone is going to respond - put that in as a feature request - but I've have had no luck for the past six years with any of my feature requests. Could be a case of Africa not being a significant player in this field or perhaps my feature requests have all been low on priority list of developers.
Hi Alphonso,
Thanks for letting us know what you'd like to see with the dial! The arc is there as a guide to show the rotation and steps when designing, but I appreciate you sharing that you'd like to have it published as well.
Here are further details on how we manage feature requests in case you were curious about the process!
Just added feature request
Ren, while I appreciate you responding - consider the following:
Maths and Science (Physics) users would like to use Articulate to produce high level maths and physics equations, such as we do when using Latex editor. Now, we not in the majority, so our requests falls on deaf ears when Articulate prioritises feature requests. End result, our requests never make it to the final implementation list. I know, I've been doing this for more than 6 years now with amazing unsuccess.
We get frustrated and opt to use other software more suited to our specific needs. And so maths and science users become even less in number and voting power when it comes to Articulate feature requests.
The point is, our numbers can never grow unless Articulate actually starts listening to our requests. We doomed to always be told: "What a great idea, why don't you submit that as a feature request."
this article still helped me, as I won't keep trying to make it work! :) Think I'll overlay a graphic to the arc.