Archive: limitations of the new page system


limitations of the new page system
The new page system in CVS looks good, but with the removal of .onNextPage and .onPrevPage, there seems to be no way to cancel moving to the next/prev page.
Here is how I use this functionality:
Between the directory page and the install page I check if the program is already installed and running (by trying to open the executable in append mode). If it's running, I tell the user to close it or select a different install location. Then I call Abort to stay on the directory selection page.

Is there really no way to do it with the new page system?


Sure there is:

Use Abort (see Section 4.8.1) from a built-in page pre-function to skip the page.

That's not what I want. I don't want to skip the page, I want to cancel moving to the next page.


Oh, well, you can use .onVerifyInstDir for this but poping up message boxes won't be such a good idea since it is called everytime the user changes the selected directory.

I will think about adding a post function to the pages.


Please add my vote for a post-page callback so I can do something when I'm leaving the page, and Abort when I don't want to leave the page.


What's your reason jbm? Why do you need it?


Same reason as I've seen posted elsewhere in this forum: I'm doing a prompt on the installdir if it doesn't exist I ask if they want to create it, and a Cancel on that dialog leaves the user on the same page so they can change it.

I understand about being able to add pages with InstallOptions and the use of .onVerify, but in this case my boss would rather see it behave "like other installers" and so I've implemented that.

Otherwise I'd be on 2.0 right now, as I'm itching to get MUI up. It's the only remaining concern for me. Maybe it should be a standard feature, as I see someone else is doing that too.


There is a pretty good possiblity it will be added to b1.