how is this still an issue 4 years after it was first mentioned?
It would be easy to implement slide and scene variables. Storyline variables exist. Slides and scenes are numbered. The framework to deliver this feature exists. That it isn't available after so many years suggests it isn't on the table for a future release either.
I think it's best not to expect Articulate to listen. Even their own staff can see there are things that need fixing or would vastly improve their productivity yet they can't be frank about what they would like to see fixed or how long, if ever, their biggest peaves will be addressed.
Wouldn't it be nice if your timeline didn't shift based on an object you paste from one slide to another? Wouldn't it be nice if your slides could automatically match your longest audio piece? Who hasn't had that problem on slide after slide and found it annoying to have to drag the timeline back where it was over and over? Has it been fixed in the years we've been using Articulate? This is basic, "Wow, what a pain in the ass this is and I wonder if they will ever fix it?" material that is obvious to anyone who isn't a casual user. There are dozens, dare I say over a hundred, of things just like that which would make this software worthy of undying love.
Instead you may just have to live with what I experience: a profitable love/hate relationship.
Regarding the request for additional system variables, we have taken a step in this direction. When we released Closed Captions, we exposed a variable that the author can target with a trigger to display or hide the captions: Player.DisplayCaptions A small hint of things to come. 😉
In addition, we don't have plans to introduce a ton of system variables at once. I say this to point out that if we do expose system variables, it will be in a targeted way that solves real business problems (such as slide numbers/page numbers, for example), not simply giving people access to 100 random system variables so that we can say we did. 😀 We'll deliver them as they are ready, and we hope to be able to share the first of these in the next few months.
We'll be taking a look at the timeline behavior you mentioned the next time we make timeline improvements, which is also on our roadmap.
I find it hard to believe that even you, Justin, aren't dismayed that your own peeves about Storyline; that after years some very basic improvements haven't been made while the focus is instead on new features.
I understand the need for Storyline to compete but it is clearly at the expense of not improving productivity. There are features that are already there but don't work the way they could in a way that would save time and hassle.
If you have ever had a customer ask for page numbers, then you would feel our pain. I have tried variables only to find that after so many times I use them on a new presentation from a template that they are jacked up. The only real solution? Use the built-in variables which aren't available in Storyline but are accessible in competing software.
And it's not just page number variables that would improve productivity. You must have some time-saving pet peeves that are going unappreciated, Justin. If you don't then you can't hear us and if you do then you must feel what we feel.
Thank you for asking. Please see my new post here. I have a module where scoring is getting all out of whack and I can't tell what is going on behind the scenes.
63 Replies
It would be easy to implement slide and scene variables. Storyline variables exist. Slides and scenes are numbered. The framework to deliver this feature exists. That it isn't available after so many years suggests it isn't on the table for a future release either.
yes, page numbers were a 'popular feature request' 4 years ago:
https://community.articulate.com/discussions/articulate-storyline/inserting-storyline-slide-numbers
I think it's best not to expect Articulate to listen. Even their own staff can see there are things that need fixing or would vastly improve their productivity yet they can't be frank about what they would like to see fixed or how long, if ever, their biggest peaves will be addressed.
Wouldn't it be nice if your timeline didn't shift based on an object you paste from one slide to another? Wouldn't it be nice if your slides could automatically match your longest audio piece? Who hasn't had that problem on slide after slide and found it annoying to have to drag the timeline back where it was over and over? Has it been fixed in the years we've been using Articulate? This is basic, "Wow, what a pain in the ass this is and I wonder if they will ever fix it?" material that is obvious to anyone who isn't a casual user. There are dozens, dare I say over a hundred, of things just like that which would make this software worthy of undying love.
Instead you may just have to live with what I experience: a profitable love/hate relationship.
We're always listening, Joseph!
Regarding the request for additional system variables, we have taken a step in this direction. When we released Closed Captions, we exposed a variable that the author can target with a trigger to display or hide the captions: Player.DisplayCaptions A small hint of things to come. 😉
In addition, we don't have plans to introduce a ton of system variables at once. I say this to point out that if we do expose system variables, it will be in a targeted way that solves real business problems (such as slide numbers/page numbers, for example), not simply giving people access to 100 random system variables so that we can say we did. 😀 We'll deliver them as they are ready, and we hope to be able to share the first of these in the next few months.
We'll be taking a look at the timeline behavior you mentioned the next time we make timeline improvements, which is also on our roadmap.
In the interim, we hope you've noticed the massive amount of new functionality we've added to Storyline 360 since its release, and please do keep an eye on what's coming next across the entire Articulate 360 suite.
I find it hard to believe that even you, Justin, aren't dismayed that your own peeves about Storyline; that after years some very basic improvements haven't been made while the focus is instead on new features.
I understand the need for Storyline to compete but it is clearly at the expense of not improving productivity. There are features that are already there but don't work the way they could in a way that would save time and hassle.
If you have ever had a customer ask for page numbers, then you would feel our pain. I have tried variables only to find that after so many times I use them on a new presentation from a template that they are jacked up. The only real solution? Use the built-in variables which aren't available in Storyline but are accessible in competing software.
And it's not just page number variables that would improve productivity. You must have some time-saving pet peeves that are going unappreciated, Justin. If you don't then you can't hear us and if you do then you must feel what we feel.
h/t and apologies to Quast.
Love that cartoon copyright 2013 no less.
This discussion is just surreal and makes me pine for Hypercard.
I have an issue right now where something is getting messed up with a system variable, and because it isn't exposed, I can't tell what is going on.
Are you asking for help Will or just making a comment?
Thank you for asking. Please see my new post here. I have a module where scoring is getting all out of whack and I can't tell what is going on behind the scenes.
Hi Will
see this post which sounds like a similar issue - not sure what support have discovered.
https://community.articulate.com/discussions/articulate-storyline/storyline-360-quiz-passing-score-doubles-on-retry-quiz
This post was removed by the author
YAY!: https://community.articulate.com/series/articulate-storyline-360/articles/storyline-360-add-slide-numbers
This discussion is closed. You can start a new discussion or contact Articulate Support.