Object Properties

Home

4D v20 R7

Object Properties

The Object Properties commands act on the properties of objects present in forms. They enable you to change the appearance and behavior of the objects while using the forms to display records and in the Application environment.

Important: The scope of these commands is the form currently being used; changes disappear when you exit the form.

Accessing Objects using their Object Names or their Data Source Names

The object property commands share the same generic syntax described here:

COMMAND NAME({*;} object { ; additional parameters specific to each command )

If you specify the optional * parameter, you indicate an object name (a string) in object.

You can use the @ character within that name if you want to address several objects of the form in one call. The following table shows examples of object names you can specify to this command.

Object Names	Objects affected by the call
mainGroupBox	Only the object mainGroupBox.
main@	The objects whose name starts with “main”.
@GroupBox	The objects whose name ends with “GroupBox”.
@Group@	The objects whose name contains “Group”.
main@Btn	The objects whose name starts with “main” and ends with “Btn”.
@	All the objects present in the form.

Form object names can contain up 255 bytes, allowing you to define and apply custom naming rules, such as "xxxx_Button" or "xxx_Mac".

Note: You can configure the way the @ character is interpreted when it is included in a character string. This option affects the functioning of the commands in the "Objects (Forms)" theme. For more information, refer to the 4D Design Reference manual.

If you omit the optional * parameter, you indicate a field or a variable in object. In this case, you specify a field or variable reference (field or variable objects only) instead of a string.

Interaction of generic commands with multi-style areas

Starting with 4D v14, interaction between generic commands such as OBJECT SET RGB COLORS or OBJECT SET FONT STYLE and multi-style text areas has been modified.

In previous versions of 4D, executing one of these commands modified the contents of any custom style tags inserted in the area. From now on, only default properties are affected by these commands (as well as any properties saved by means of default tags). Custom style tags remain as they are.

For example, given a multi-style area where default tags were saved:

The plain text of the area is as follows:

<span  style="text-align:left;font-family:'Segoe  UI';font-size:9pt;color:#009900">This is the word <span  style="color:#D81E05">red</span></span>

If you execute the following code:

OBJECT SET COLOR(*;"myArea";-(Blue+(256*Yellow)))

With 4D v14 and next versions, the red color remains:

4D v14 and higher	prior versions

`<span style="text-align:left;font-family:'Segoe UI';font-size:9pt;color:#0000FF">This is the word <span style="color:#D81E05">red</span></span>`	`<span style="font-family:'Segoe UI';font-size:9pt;text-align:left;font-weight:normal;font-style:normal;text-decoration:none;color:#0000FF;"><span style="background-color:#FFFFFF">This is the word red</span></span>`

The following generic commands are concerned:

OBJECT SET RGB COLORS
_o_OBJECT SET COLOR
OBJECT SET FONT
OBJECT SET FONT STYLE
OBJECT SET FONT SIZE

In the context of multi-style areas, generic commands should be used to set default styles only. To manage styles during database execution, we recommend using the commands of the "Styled Text" theme.