Allow shapes outline to be inside or outside, not only middle?

@Phil I gloss over it because... Vast majority of my projects (and I do a lot of them through the year) doesn't require WCAG support. And, sadly, adding support point by point every update doesn't change a thing - project from Storyline would not be WCAG compliant. It won't pass the requirements. Also, these added points are... well, storyline-like - they are often broken. You can do really simple WCAG course, but nothing more complicated than a screen with text and maybe a layer. But of course there is improvement in Accesibility features and I won't deny it. know it takes time, but...

But look at the list, add WCAG-partial-support. Do you really think that multimilion company cannot do better, at least at repairing bugs from 10 years ago or from new features? I really don't mind about new features, I'd just love to have bugfree environment in which I can work flawlessly. I can manage with new functions on my own through webobjects and javascript, if I ever need to. But I can't change internal code so the lines doesn't change width and height randomly or - yesterday case, when suddenly all my circular buttons went elliptic. Twice. On new project.

@Math thanks for the supportive vote. I've seen your feature list earlier, but this is unofficial. If someone uses forums, maybe they stumbled upon it. But most users won't see it. And you know about the flaws of it too :) But Articulate should be learning from you, that this can be done and is needed. I don't really have a problem that MINE ideas are not implemented (of course I see them the most fitting :D), I have a problem that bugs are being added and not addressed. And if bug exists, it shouldn't have 200 people to report it - ONE PERSON should be enough. This. Is. A. Bug. It doesn't work as intended. That's broken software for which company charges plenty of money.

Timeline speed feature affects 10-years-ago courses, when you put text on the screen, you give some voiceover and block next button until voiceover is done. This is really not the path that any e-learning serious company should take. This is first and foremost annoying 'feature' of all e-learning trainings that I've heard from users. If you block them from progressing because someone is reading something, or when you need to click 10 buttons with plus mark to show next bullet on the list. That's not how e-learnings should work. Thanks whatever in heavens that this trend passes away. But some people still do this in this manner... and well, that will be beneficial for users, so for me that feature is not hot nor cold. To be honest I haven't used built-in seekbar for like 8 years. Not a single company has ever asked me of such a feature. And if they do, I'll be very strict not to do so. Well I hardly even user voiceovers these times and generally this is favorable by users :D

I really, really hope that Storyline won't fully go SaaS. This is taking all of your developing freedom from you. You'll be only able to make simple e-learnings with this. Well for me, if SL go fully webbased SaaS, will be the end of the e-learning developer career. Everything will look the same and have the same functions. Brrr ;) The same goes with SL for Mac - as we can see, company doesn't handle well bugs and new features. Now, double the work they have to do. We will get new function once a year ;)