Tags in the model object: When the expression to complete can be resolved to a concrete entity in the embedded model, completions are available for the methods in the model object API that take a first argument that is a tag in a list, as shown.

The list above comes from an application whose embedded model contains two plot groups (pg1 and pg2). The completion list contains both the tags and the names of the corresponding plot groups. To transfer only the tag to the code, choose a completion in the list and then press Tab.

Types in the model object when creating new entities: When the expression to complete can be resolved to a concrete entity in the embedded model, completions are available for operation types in the model object when creating a new node.

Property names: When the expression to complete can be resolved to a concrete entity in the embedded model, completions are available for property names used as first arguments to the get and set operations. These are available for most features in the model object.

The example above shows the properties that are available for the plot group pg1 in the embedded model. If you select an entry in the list, you see the property’s description and its data type. When available, you may also see a link to the documentation and a set of allowed values. The allowed values appear if the set of allowed values is a finite array of strings.

Property values: When the expression to complete can be resolved to a concrete entity in the embedded model, completions are available for property values used as second arguments in the set operations that are available for most features in the model object.

If you select an entry in the list, you see the property value’s description and a link to the documentation, if available.

When hovering over different parts of the code for a method, tooltips appear to provide information about that part of the code. The following tooltips appear for different parts of the code:

When you hover over a property name for a model or application object property, you get information about the property, similar to what you see for the property when code completion is used. For example, if you hover over numerical in model.result().numerical(“gev1”).setResult();, you see the following tooltip.

If you hover over the same property’s model entity name, “gev1” in this case, you see the following tooltip with information about the purpose of the model entity.

For variables defined under Declarations in the Application Builder tree, the variable’s description appears as the tooltip when you hover above them. In this case, it is the string variable inXpolRatio.

For shortcuts to form objects, also defined under Declarations, the description and the corresponding Java code appear in the tooltip. In this case, it is for the shortcut with the name labelinXpolRatio.

In the Methods page under Application Builder in the Preferences dialog box, you can specify options for code generation and completion.

The Close brackets automatically check box is selected by default. The software then automatically inserts a corresponding closing bracket if you type a {, [, or ( character. Clear the check box to disable the addition of closing brackets.

The Generate compact code using ‘with’ statements check box is selected by default. The generated code uses with statements to set a target to use with the coming calls to set(), setIndex(), getString(), and so on, which makes the code more compact. Clear the check box if you prefer to use the full code without the use of with statements.