Flash Drawing Control

Drawing Panel Options

Note: With the release of ARCHIBUS V.23.2, all ARCHIBUS views were converted to use the HTML drawing control instead of the Flash drawing control. If you have previously created views that use the Flash drawing control, the view's drawings will still work.

For new views that you create, ARCHIBUS, Inc. recommends using the HTML control, as the Flash control is slated for desupport in future versions of ARCHIBUS. For information on converting existing views with Flash drawings to HTML format, see Convert views with the Flash drawing control to the HTML drawing control. The following is a list of all drawing panel attributes:

Name Description Default Value
type "drawing" (Required)  
id The id used for referencing this panel (Required)  
highlightDataSource The name of the data source that determines what assets are highlighted. (Optional) none
labelsDataSource The name of the data source that determines the text labels. (Optional) none
highlightType

“thematic” – Apply different colors for values of a particular field.

“restriction” – Apply the same color for a particular restricted database query.

(Optional)

‘restriction’
thematicHighlightStyle

“predefined” – Assets use the highlight colors in the database.

“automatically assigned” – Highlight colors generated on the fly.

(Optional)

Note: Even if ‘predefined’ is set, values with no assigned hpattern_acad value will use a color from the ‘automatically assigned’ list.

‘predefined’
projectionType

“tiled” – Multiple floor plans displayed in array layout.

“isometric” – Multiple floor plans are displayed isometrically.

(Optional)

‘tiled’
columnsGroupedBy When laying out multiple floor plans, this attribute determines how they will be visually arranged in the view. Example, floors from multiple buildings are displayed, using ‘bl.bl_id’ in this case will ensure that floors in the same building are grouped together. (Optional) none
assetTypes A comma delimited list of asset type files to load. e.g. ‘rm’ or ‘su’. Currently only 1 asset file can be loaded. (Optional) ‘rm’
legendPanel The id of a grid panel that is used for the legend. See the Legend Panel section for more information. (Optional) none
initialData The primary key of a drawing file to load on startup. e.g. [ "fl.bl_id", "hq", "fl.fl_id", "18"] (Optional) none
multiple Controls whether or not more than 1 drawing can be loaded at a time. A Boolean. (Optional) true
selectionMode

Controls which assets if any are selectable. Possible values are:

0: None

1: Only assigned assets (per the highlightDataSource)

2: All

(Optional)

2
multipleSelectionEnabled Allows multiple assets to be selected. A Boolean (Optional) true
assignMode

Controls how the Drawing Control supports assignment logic. Possible values are:

0: Disabled

1: One to One

2: One to Many

3: Many to One

4: Many to Many (Not currently supported)

See the assignMode section below for more information.

(Optional)

0
toolbarSettings

(Optional) Controls certain aspects of the Drawing Control Toolbar during initialization of the control itself.

Format: action1=commaDelimitedListOfButtonNames;action2=...

List of valid actions:
     show
     hide
     enable
     disable

List of currently supported button names:
    all
    state (group of state buttons are only supported as group:
                select, pan, and zoomWindow)
    resetAssets
    clearAssets
    zoomIn
    zoomOut
    autoScale
    autoCenter
    iso

Example Usage:

   show=resetAssets,clearAssets;
    hide=iso;
     enable=iso,autoCenter;
    disable=zoomIn;
    hide=all;
    hide=zoomOut;
    disable=autoScale,iso,etc;

 

assignMode Attribute

The Drawing Control has built in logic to aid in supporting Assignment type of functionality in an application. By default, this logic is disabled unless specifically specified to enable per one of the supported modes as described in the ‘Options Attributes’ table listed above. The following table describes the logic that is enabled per these different modes. Note: Specifying any of the modes other than Disabled will override the ‘multipleSelectionEnabled’ (if that is set).

Assign Mode Behavior
0 Disabled As assets are selected, their fill properties will be set to the ‘selected’ fill style. As assets are unselected their fill properties will be set to the ‘unselected’ fill style. This is the default behavior.
1 One to One

The type of scenario that this would be support would be when assigning a single value to a single room, such as 1 employee per room. This is typically driven by a grid control that passes a value (such as an Employee name) to the Drawing Control. The following describes how clicking on assets (rooms) affect the fill color of those selected assets:

Asset is clicked on: Fill color changes to unique color, per the value. onclick event is fired with the selected asset id and a selected state of ‘true’.

Different asset is clicked on: Fill color of different asset changes to the same unique color per the value. Previously clicked on asset reverts back to the ‘unselected’ fill color. onclick event is fired with selected asset id and a selected state of ‘true’

Same asset clicked again: Unselects that asset, reverts the fill color to be the ‘unselected’ color. onclick event is fired with selected asset id and a selected state of ‘false’

Another value passed in to the Drawing Control:

An asset that hasn’t been previously selected: Fill color changes to unique color, per the value. onclick event is fired with selected asset id and a selected state of ‘true’

A previously selected asset per a different value: Nothing happens, only one value can be assigned per asset. onclick event is not fired.

2 One to Many

The type of scenario that this would support is where a single value, such as a Room Standard, would be assigned to multiple rooms. This is typically driven by a grid control that passes a value (such as a Room Standard) to the Drawing Control. The following describes how clicking on assets (rooms) affect the fill color of those selected assets:

Asset is clicked on: Fill color changes to unique color, per the value. onclick event is fired with the selected asset id and a selected state of ‘true’.

Different asset is clicked on: Fill color of different asset changes to the same unique color per the value. Previously clicked on asset retains that same unique color. onclick event is fired with selected asset id and a selected state of ‘true’

Same asset clicked again: Unselects that asset, reverts the fill color to be the ‘unselected’ color. onclick event is fired with selected asset id and a selected state of ‘false’

Another value passed in to the Drawing Control:

An asset that hasn’t been previously selected: Fill color changes to unique color, per the value. onclick event is fired with selected asset id and a selected state of ‘true’

A previously selected asset per a different value: Nothing happens, only one value can be assigned per asset. onclick event is not fired.

3 Many to One

The type of scenario that this would support is where multiple values, such as employees are assigned to a single room. This is typically driven by a grid control that passes a value (such as a Room Standard) to the Drawing Control. The following describes how clicking on assets (rooms) affect the fill color of those selected assets:

Asset is clicked on: Fill color changes to a unique color, per the selected asset. onclick event is fired with the selected asset id and a selected state of ‘true’ and the color applied.

Different asset is clicked on: If there are no other assignments made to this selected asset, then the fill color changes to a unique color, per the selected asset. If there already is a previous assignment to this asset, the existing fill color will be retained on that asset. If the previously clicked on asset still has 1 or more other assignments, then it retains that same unique color associated with that asset. If he previously clicked asset has no other values assigned to it, then the fill color will revert back to the ‘unselected’ color. In any of these cases, the onclick event is fired with selected asset id and a selected state of ‘true’

4: Many to Many Not currently supported
Copyright © 1984-2018, ARCHIBUS, Inc. All rights reserved.