Forum Discussion
Overlapping States
Thank you for sharing what you're experiencing regarding object states in Storyline, JeffForrer.
I understand how this can be a pain point for your development work. We're still gathering votes for this request so our product team can work on modifications.
We'll update this discussion once there are changes that might help, and you'll be among the first to know!
Forgive me for asking, but how is a development team gathering votes to fix a critical bug that has existed in the product for years and has caused substantial customer complaints? I do not mean that rhetorically, I am truly curious how this process works. We've all been asking for transparency from Articulate, and for some reason this issue receives little, which creates further frustration - which I hate to see, as I know you all are doing great work.
It's frustrating and bittersweet seeing things like Premium AI features being added to Storyline, when these features ignore years of customer complaints for efficiency and reliability. Perhaps with all the extra money being made from these newly added Premium AI features, Articulate could consider fixing it's cracked foundation? I truly don't mean any offense, but this support case alone has been open for almost four years.
I agree. This issue is not a "nice to have", it actually impacts work produced with the product. It seems as if Articulate does not care about the actual issues with functionality, as long as they can continue pushing new features with pizzazz and charge more. Didn't the cost of a single license rise again this year?
Hi Spencer!
No worries! No offense was taken from your post! I completely understand this has been an ongoing setback for you.
I would like to first thank you for being so active in this discussion. You’ve been keeping the conversation going, and assisting other users who were facing the same frustrations. I also recognize your proximity to this issue is significant, as you were the user who initially started this discussion.
Our goal is never to neglect a critical bug, or leave our authors stuck in their development. The voices of our users are consistently being heard and shared with product managers. The development team follows an order of priority, with the most impactful issues being addressed first. We approach each issue with consideration of how the implementation of a fix would impact other areas of Storylines' architecture. Occasionally, this process requires more thorough collaboration, across multiple teams.
I’ve shared your comments in this discussion with our product managers so they are updated on the impact. I don’t have any additional details to share but when I do, I’ll be sure to update this discussion.
It is funny that Articulate are "gathering votes" to address this bug, which, y'know, is such a hard and complex thing because never in the history of online development has ANYONE used a HOVER state on a button before and these things are obviously so complicated and... what is the word I'm looking for... TECHNICAL–that's it–no one in the Articulate development team knows what buttons are supposed to do so, yes, it is obviously time consuming, and, well, honestly, four years isn't really that long a time to try and figure out how buttons work and, y'know, QA testing is HARD and maybe most people will not notice and someone in the community will figure out a new hack (that Articulate somehow 'broke' and don't know how to 'unbreak' that 'fix') and all will be good with the world again and people will pay lots of money for AI and 360º and boxes that cannot be rounded to specific units and no shape editing features and lack of SVG editing and all that other stuff no one has ever needed in the history of eLearning development.
