Action is not executed - why?

[hsc]

Hi,
the attached screenshot shows a custom dialog with a push button, this button's published events, and its properties. The question I have about this is: When the button is pushed, the 3rd published action is executed, and so is the 5th, but the 4th action isn't. Is there an obvious error in the button's configuration, or something else that escaped my attention?
The log file (created with /L*V) containes these two lines immediately following each other, with no indication of the child dialog in between:

Code: Select all

MSI (c) (14:C0) [08:06:27:770]: PROPERTY CHANGE: Modifying USING_CORP_REG property. Its current value is 'False'. Its new value: '<<BEFORE>>'.
MSI (c) (14:C0) [08:06:27:770]: PROPERTY CHANGE: Modifying USING_CORP_REG property. Its current value is '<<BEFORE>>'. Its new value: '<<AFTER>>'.

(I temporarily borrowed the USING_CORP_REG property from elsewhere in this installer project.)
I tried several variations (like using "True" as condition or disabling actions 1 and 2, as in the screenshot) but with no effect.

[Catalin]

Hello Hans,

This is interesting, indeed.

To be honest with you, I can't say for sure why the event is not triggered.

However, I might have a hunch and that is the condition. What is that "True", is it a property?

For instance, if you change the condition to something that's always true, does it execute?

Such condition could be "1=1".

Best regards,
Catalin

[hsc]

Hello Catalin, thank you for your reply. The condition was initially just "1", and that had the same effect. I found "True" mentioned in some places (and it would be a natural choice for a true logical condition), so I though I'd try it. However, I found that it worked much better after I removed the last action (Refresh the current dialog). Now I am a few steps further down the way.

Best, Hans

[Catalin]

Hello Hans,

Thank you for your followup on this!

I am glad to hear you managed to get this to work.

Thank you for sharing the solution with us - I'm sure other users facing a similar scenario will find this useful.

Best regards,
Catalin