Alright, I have some new discoveries about this Bob :-)  It turns out that I
do not have to publish the Reset even to get the dialog to refresh itself.
Here's what seems to be happening:

IF I only publish the "DoAction" event that sets my "My_ProdVerified"
property, the icons (checkmark or an "X") that conditionally rely on this
property to not react.  If after my "DoAction" event I publish the
following:

<Publish Property="TEMP_VERIFIED" Value="[My_ProdVerified]">1</Publish>
<Publish Property="My_ProdVerified" Value="[TEMP_VERIFIED]" />

The icons display like they are supposed to.  Is this normal behavior?  That
setting a property from a CA would be different than doing the <Publish
Property="".../> thing?

On 1/11/07, Bob Arnson <[EMAIL PROTECTED]> wrote:

Levi Wilson wrote:
> As well as the MaskedEdit I guess too?  Because I enable/disable it as
> well based upon that.  There must be a special case for CheckBox
> buttons?  Becuase I have an Edit control in another dialog that has
> enable/disable condition actions based upon the property that a
> CheckBox sets/clears, and that works.

Many frameworks have the concept of "command enabling" so buttons and
even check boxes kinda make sense, as they're commands. Edit controls
aren't; icons are usually static. I think it just doesn't fit the 80
percent model MSI UI supports.

--
sig://boB
http://bobs.org



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users

Reply via email to