Regardless of whether I press F5 or Shift+F5 to run the prototype it always starts with the currently displayed screen. How can I get it to start from the "beginning" of the prototype?
--- Thanks, Jeff
Ack! That's not good. Sounds like a bug. I'll wait for our engineering jedi team to respond to this one.
Are you talking about different screens? The F5 runs the current screen from the previous state (to quickly test the interaction / animations of the current state) and Shift+F5 runs the current screen from the Start state (to quickly test the screen as a whole) but it always runs the currently active screen.
If you're in the Project Home F5 it runs from the Home Screen. Do you expect that F5 runs from the Home Screen even if it’s different from the one you’re designing at the moment?
Yes, that was my expectation - i.e. that it works similar to PowerPoint (showing my bias here :-) In PowerPoint, F5 will start the presentation from the first slide whereas Shift+F5 will start from the current slide.
In my current prototype that I'm working on, I have several screens (~8 or 9) and most of those have only the "start" state (some have animations). I would like the ability to run the prototype from the first/top-most screen as well as from the current screen (whether that's a modification to the existing hotkeys or an additional hotkey).
After some discussion, we think we can tweak our shortcuts to accomodate this pattern. So F5 will run from app home; Shift+F5 will run from start of selected/current screen, and Ctrl+F5 will run from current state of current screen. We have that extra scope to deal with, and we originally made it the way it is because Indigo is currently biased a bit more towards the state-driven approach.
We'll let ya know when we have the update released.
That's awesome news! Thanks!