3 replies to this topic

[spdygnlz]

I've got what seems like it should be a really simple dialog problem... so much I'm almost embarrassed to ask. Anyway...

I have a checkbox on a dialog that I want to be disabled by default. I set the value property of the checkbox to 1, added a property to the checkbox, added the property to Property Manager and set the value to 0.

I thought that would make it unchecked by default. What I'm seeing is that the checkbox is checked, property is still 0, but they will sync up when I uncheck and recheck the checkbox. What am I doing wrong?

[Glytzhkof]

This is a very silly design by MSI, but in order to uncheck the box you need to make sure the property is undefined rather than set to 0. This means you should remove the property from the property table and any command line entries. I am not 100% sure, but I believe you can undefine an existing property by setting it equal to an empty string like this: PROPERTY = {}

[spdygnlz]

Ahhh. thanks. That is pretty silly.

So if I do a comparison against a property that hasn't been defined yet, will that cause any problems? I'm only using something like :

PROPERTY = 1
and
PROPERTY <> 1

Would those still return the same results I'm expecting?

[Stefan Krueger]

If the property is undefined, a = comparision will result false, and <> will result true, just like you would expect it.