ScreenSteps 2.0.2 Released for Windows and Mac
ScreenSteps 2 has now been released for Windows. We have also pushed a 2.0.2 release for Mac. This update fixes a lot of bugs and adds some very useful enhancements, including:
- Improved PDF Export (Images are clearer)
- Split Lesson at Step contextual menu option. This is handy if you decide after the fact to split up your lesson into smaller bits.
- Split Step at Text. This is really cool, especially for updating old documentation you might have. See this lesson.
- Import and Export ScreenSteps Lesson Packages. This allows you to move lessons between libraries and share them with other users of ScreenSteps. See this lesson.
- Insert tabs in text fields. You can now option-tab (Mac) or alt-tab (Windows) to insert tabs in your Step instruction fields.
You can download an update or free trial here. You can also read the full release notes here.

February 21st, 2008 at 11:11 am
Hello,
I just finished demoing your ScreenSteps application (found via TUAW) to write an impromptu guide to a new web application I just deployed, and I must say, amazing. I was fretting having to documenting the process when I remembered I had bookmarked your app and I'm glad I did. While an amazing tool and resource, it's not without some minor bits that I'd like to point out in hopes that you are or will now update them.
Again, great tool! I look forward to seeing it's development.
Cheers.
February 22nd, 2008 at 10:52 am
Hi Omar,
1) There is actually a keyboard short cut for this, I'm just not sure we have it documented anywhere. Shift + Command + D on OS X and Shift + Control + D on Windows.
2) "Check Spelling While Typing" is something we would like to have in the future. Spell checking of the lesson should work though. The lesson description isn't being spell checked in the current version of ScreenSteps but this will be addressed in 2.0.3. If you are having other problems please using the Help->Email Feedback link in ScreenSteps and we can figure out what is going on.
3) This is coming.
4) I hadn't noticed this before but can confirm the bug. We are looking into it.
Thanks for the feedback.