How the Front Panel Is Assembled: Precedence Rules

The Front Panel is assembled from all the configuration files located on the actions database search path.

Where there is a conflict between components of the definition, precedence rules determine which definition is used. Two components are in conflict with one another when they:

• Have the same control name, CONTAINER_NAME, and CONTAINER_TYPE.

• Compete for the same position (by having different names but the same CONTAINER_NAME, CONTAINER_TYPE, and POSITION_HINTS).

The Front Panel uses the following precedence rules:

• If components have the same control name and container name and type, the component read first is used.

  For example, if both a system-wide and built-in control contain these fields but are otherwise different:

  	CONTROL TextEditor
   	{	
   		CONTAINER_TYPE				BOX
   		CONTAINER_NAME 			Top
   		…
   	}

  then the system-wide control has precedence.

• If two components complete for the same position, they are placed in the order in which they are read.

  For example, if a user creates a new personal control for the Main Panel (CONTAINER_TYPE BOX and CONTAINER_NAME Top) and assigns it POSITION_HINTS 5, the personal control will bump the built-in control and all other controls with higher position numbers one position to the right.

  ---

  Note –

  When you are modifying a control by creating a new system-wide or personal version of it, the new control definition must specify the same control name, CONTAINER_NAME, and CONTAINER_TYPE. Otherwise, the new control will appear in addition to the existing control.

  ---