Why the term, "value", is used for "label" control?

[sudip]

Hello Roberto,

Since I started HMG, one very silly question is coming to my mind. Why you used the term "value" for "label" control, not "caption"? I guess there must be a reason for this. I think, what we called "caption" in other software tool (eg., VFP) is actually "value" of the "label" control. Am I right?

Thanks in advance.

With best regards.

Sudip

[Roberto Lopez]

Hello Roberto,

Since I started HMG, one very silly question is coming to my mind. Why you used the term "value" for "label" control, not "caption"? I guess there must be a reason for this. I think, what we called "caption" in other software tool (eg., VFP) is actually "value" of the "label" control. Am I right?

Thanks in advance.

With best regards.

Sudip

I've took the idea of 'Value' from VFP. It signals the content for the most important property in a control, that usually comes from user interaction.

In my TODO list is the creation of synonyms for 'value' property for all controls using it.

In the case of Label, could be good that the synonymous be called 'Caption' of course.

[sudip]

Hello Roberto,
Thanks a lot

[Rathinagiri]

Nice discussion here.

IMHO, I like the property "value" than "caption" for label. (I didn't use VFP and jumped from clipper to HMG)

[sudip]

Nice discussion here.

IMHO, I like the property "value" than "caption" for label. (I didn't use VFP and jumped from clipper to HMG)

Rathi,
My path was Clipper -> VFP -> HMG. But, I also agree with you Because, IMHO, what we called "caption" in VFP is actually "value" of label. Eg., in Checkbox control, "value" and "caption" properties are different.

I haven't used VFP above 6. But, saw MS used "text" property instead of "caption" in VB.Net.

BTW, can we have default property for each control in future? In most cases it will be "value"