7 Replies
Brian Dennis

I've lost dozens hours too, but technically there's no action the SL2 code can track (unlike (key press, object move, etc). At the risk of geek speak, the re-flow is (upped) in SL2's (stateless) rendering call to the host operating system I'm betting.

Software developer myself who should have known better... repeatedly; go figure

Leslie McKerchie

Hi Edward!

It's best to change the story size before you add any slides. Otherwise, you may need to resize or rearrange objects in your story to accommodate its new size.

Did you utilize this choice:

If you decrease the story size, choose one of the options in the section that appears called If new size is smaller:

You can read about it in this tutorial.

Hi Brian!

We have seen you helping out a lot and we appreciate it, and hope you’ll continue to contribute worthwhile discussion according to our philosophy here.

Edward Hoke

Hi Leslie & All:

Thank you for your suggestion.

Since design is an iterative process, and one does not always know exactly how things will look a day, week, or a month in advance, it may not happen that a screen size gets locked-in prior to development. In a perfect world sure - but design is not that.

Captivate does allow full "undo" - just sayin' :)

I don't think this is unreasonable for your Design team.