Hi,
Is there a specific reason why we cannot put them in the correct order and have it work as expected, this seems like a bad design to me.
We are using these restrictions in order to maintain the efficiency and functionality of the dialogs used in the installation.
Let's take the "SetupTypeDlg" dialog as an example:
The dialogs you see in the "First Time Install" directory are the main dialogs of the installation. If you click their plus ("+") signs you can see their child dialogs (which are launched by controls on the parent dialog).
When you add a custom dialog and you want to place it after the "SetupTypeDlg" dialog, this custom dialog can only be a child of the "SetupTypeDlg" dialog (the custom dialog will be launched by a control on the "SetupTypeDlg" dialog).
With this scenario it is impossible for us to determine automatically which button (Typical, Custom, Complete) will launch the custom dialog (the "SetupTypeDlg" dialog had three different outputs).
So essentially we have to trick the installer into thinking that the dialog is really in a different order.
You don't have to trick the installer, you simply customize the dialogs and their order.
The treeview just shows a generic sequence path. But the actual sequence depends on your button events.
Perhaps an additional feature here could be a button that shows a graphical display of the actual sequence, much like the graphical overview of a relational database model.
Note that the sequence shown in the "Dialogs" page
is the actual structure and order of the dialogs. This is why when you add a custom dialog after the "SetupTypeDlg" dialog the custom dialog will be moved and will become a child of the "SetupTypeDlg" dialog.
Regards,
Cosmin