Quantcast

Extending WiX UI

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Extending WiX UI

Christopher Painter-2
I'm using WiX UI. In one scenarior I'm using Publish elements to insert
ControlEvent rows to get the change I'm looking for.  In another scenario I
want to disabled a control?  (CustomizeDlg  Browse control ).

I'm not being very clever in thinking of a way to do this. I was hoping to
do something like the Publish element to insert a ControlCondition row that
would disable the control  but the Control element doesn't seem to allow
this type of pattern.

Does anyone have any tips?  

Thanks,
Chris


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Extending WiX UI

jhennessey
Well this isn't exactly pretty but I did find a way to do what you want. You can create a CustomTable element for the ControlCondition table and then add rows as you need them (WiX didn't seem to mind that this was a standard table).

Here's the WiX authoring for the ControlCondition table:

    <CustomTable Id="ControlCondition">
      <Column Id="Dialog_" KeyTable="Dialog" KeyColumn="1" Category="Identifier" Type="string" PrimaryKey="yes"/>
      <Column Id="Control_" KeyTable="Dialog" KeyColumn="1" Category="Identifier" Type="string" PrimaryKey="yes"/>
      <Column Id="Action" Category="Text" Type="string" PrimaryKey="yes"/>
      <Column Id="Condition" Category="Condition" Type="string" PrimaryKey="yes"/>
    </CustomTable>

Here's a non-sensical example of adding a row:

<CustomTable Id="ControlCondition">
      <Row>
        <Data Column="Dialog_">WelcomeDlg</Data>
        <Data Column="Control_">Title</Data>
        <Data Column="Action">Disable</Data>
        <Data Column="Condition">NOT Installed</Data>
      </Row>
    </CustomTable>

Note that the table definition can be in separate fragment from the data. Also, I think it would probably be a good idea to file a bug or feature request to make this easier to do.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Extending WiX UI

Christopher Painter-2
In reply to this post by Christopher Painter-2
Heh, I should have been able to think of that one! LOL

Thanks.   You are right, not elegant, but in this case, I'll take it.

My question stands though, I'd like to have a better understanding of ways
to manipulate the UI authoring provided by the extension.

----------------------------------------
 From: "jhennessey" <[hidden email]>
Sent: Thursday, July 26, 2012 11:57 AM
To: [hidden email]
Subject: Re: [WiX-users] Extending WiX UI

Well this isn't exactly pretty but I did find a way to do what you want.
You
can create a CustomTable element for the ControlCondition table and then
add
rows as you need them (WiX didn't seem to mind that this was a standard
table).

Here's the WiX authoring for the ControlCondition table:

<CustomTable Id="ControlCondition">
<Column Id="Dialog_" KeyTable="Dialog" KeyColumn="1"
Category="Identifier" Type="string" PrimaryKey="yes"/>
<Column Id="Control_" KeyTable="Dialog" KeyColumn="1"
Category="Identifier" Type="string" PrimaryKey="yes"/>
<Column Id="Action" Category="Text" Type="string" PrimaryKey="yes"/>
<Column Id="Condition" Category="Condition" Type="string"
PrimaryKey="yes"/>
</CustomTable>

Here's a non-sensical example of adding a row:

<CustomTable Id="ControlCondition">
<Row>
<Data Column="Dialog_">WelcomeDlg</Data>
<Data Column="Control_">Title</Data>
<Data Column="Action">Disable</Data>
<Data Column="Condition">NOT Installed</Data>
</Row>
</CustomTable>

Note that the table definition can be in separate fragment from the data.
Also, I think it would probably be a good idea to file a bug or feature
request to make this easier to do.

--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Extending-WiX-
UI-tp7579571p7579573.html
Sent from the wix-users mailing list archive at Nabble.com.

----------------------------------------------------------------------------
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
WiX-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/wix-users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate
star

Re: Extending WiX UI

jhennessey
Take a look at this (if you haven't already): http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm

I usually end up just copying from the existing source and creating my own dialogs and dialog sets. Since you can't easily extend all parts of the existing extension (like easily adding control conditions).
Loading...