There is a multitude of interfaces and rules to be respected. Often, these constraints are linked to the domains of activity. Obviously, some data can be entered or not by the user. For a field that is not enterable, there are two ways of managing the interface:
- users can still select and copy its content, for example to add it to a report
- users are not allowed to copy the field or select its content
To allow you to manage all these interface possibilities, the OBJECT SET ENTERABLE command has been enhanced. As a last parameter, the command now supports an integer. This allows you to have a better control over the focusable property for your field. The possibilities are:
- 0 – non-enterable, and its content can be selected,
- 1 – enterable,
- 2 – non-enterable, and its content cannot be selected.
OBJECT SET ENTERABLE(*; "Input"; obk not enterable)
OBJECT SET ENTERABLE(*; "Input"; obk enterable)
OBJECT SET ENTERABLE(*; "Input"; obk not enterable not focusable)
Of course, you can use the command as before by passing a boolean as a last parameter. Keep in mind that in this case, the focus status for a non-enterable field differs between binary and project mode. You can find the details of all combinations in the documentation.
- False – non-enterable,
- True – enterable
OBJECT SET ENTERABLE(*; "Input"; False)
OBJECT SET ENTERABLE(*; "Input"; True)
For more details, the documentation for the OBJECT SET ENTERABLE command is here.