Forum Discussion
Storyline Spell Check Issues
Good Morning Community!
This morning, myself and another Storyline user seem to be having issues with the spell check feature in Storyline.
Here's the details...
When you attempt to use the ...
Hello everyone!
Good news! Today, we just released Storyline 360 Update 78 (Build 3.78.30680.0) which includes a fix for the bug where auto-correct in Notes shows options, but clicking those words doesn't change the incorrect word.
Now all you need to do is update Storyline 360 in your Articulate 360 desktop app!
If you have additional questions, don't hesitate to reach out in this discussion or in a support case.
Still happens regularly, underlined red error identified by storyline, right click on the word.
Correct spelling shows in the list.
Left click on correct spelling and it's 50/50 whether it will take.
Will always keep failing after it does it the first time.
Hi Mike,
Thank you for letting us know. I am sorry that you are encountering this snag.
May I ask if you could share a screen recording of the issue? We have had some challenges recreating this issue, so any other details you can share would help out greatly!
I look forward to hearing more as we get to the bottom of this!
Hi Vincent, I've had the above problem too for many months - over different contracts so many different projects and even Articulate licenses I get a red wavy line when the word is incorrect I right click and see the options but if I click an option the word doesn't change. So now I just look at the correct spelling and change the word manually but today I thought I'd finally get around to reporting it.
A Peek recording of this can be viewed here: https://360.articulate.com/review/content/12029188-4ecd-46a9-ad9b-5ea8c8cb9866/review
Hello Elizabeth!
Thank you for sharing this with us! I've tested this on my end, but I do not see the red wavy line stay. Here's my test.
I've tested this using Storyline 360 (Build 3.47.23871.0). Are you using this version as well?
Once I gather more details on where you see this snag, I'll create a bug report. Thanks for troubleshooting this snag with us!
