| Subject: | a better way to skip pages |
We need a better way to skip pages at runtime (e.g. if the user says
on page 2 that they don't want to install feature B, then later on we
want to skip over page 5 that performs the feature B installation).
I've been using the postNextButton callback to dynamically determine
when to jump past certain pages; this code is ugly, you can see the
pages flip by in the GUI, and if the user clicks "back" they can see the
pages that got auto-skipped. Peter from Austria wrote functions to
physically delete/insert pages into the stack at runtime; this is
better, but what if the user goes back and you need a deleted page again?
I propose a mechanism whereby each page can be marked as "skip".
During the internal page transition, the "skip" flags are examined to
determine which page to actually go to.
--
- - Martin 'Kingpin' Thurn