In article <[EMAIL PROTECTED]>,
Dean Ward <[EMAIL PROTECTED]> writes:
> I'm currently creating some custom actions using DTF that also have some
> custom UI stored in a .wixlib. Right now these have some well-known
> properties that are used. However, I have a situation where I have the same
> dialog that needs to be used several times within the same installation.
> E.g. I need to select several IIS sites. In this scenario it would be
> helpful to assign the results of each IIS site selected into separate
> properties.
>
> Is this possible? I suspect not because once a dialog is referenced it is
> effectively a singleton. Is there any way of doing this in a different
> fashion? I've done a fair bit of searching around this, but have come up
> with no results so far. Any help will be greatly appreciated!
The way to do this is to parameterize the dialogs with indirect
properties.
Typically you use a dialog to get some user input and store that into
a property. Each property that holds the data is associated with the
corresponding control on the dialog.
To parameterize this, you use indirect properties. With an indirect
property, the property associated with the control holds the name of
another property that will hold the data. Specify 'Indirect=yes' for
the controls associated with indirect properties.
Then, when you want to spawn that particular dialog, sequence a bunch
of set property events or type 51 CAs to set the names of the
properties to be loaded with data by that dialog, then spawn the
dialog. To subsequently select the data with the same dialog into
different properties reset the control properties to contain the names
of the new properties and spawn the dialog again.
While a dialog can only appear in the UI sequence once (since it has
to be unique), this is just the starting point for a wizard sequence.
Once you are in the wizard sequence you can spawn the same dialog as
many times as you like. Of course, if you plan on reusing the same
dialog in the Next/Back wizard sequence itself, then you'll need to
have some sort of logic to determine where you are in the sequence of
repeated dialogs to get the correct next/back behavior on the buttons
and on the properties used to control the dialog. I suspect that
you'll still need to do NewDialog even if its the same dialog because
of the interaction with the indirect properties.
--
"The Direct3D Graphics Pipeline" -- DirectX 9 draft available for download
<http://www.xmission.com/~legalize/book/download/index.html>
Legalize Adulthood! <http://blogs.xmission.com/legalize/>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
