DriveWorks Solo 24

System Color Conversion

System Color Conversion

From DriveWorks 24.1 onwards, any color property that references a System color (for example ControlText) will be automatically converted to a hex color when rendered on a Form (for example #000000).

This ensures system colors render the same color across desktop, all browsers and all color schemes (light/dark).

Prior to this release, system colors were automatically converted from the .NET system color (for example ControlText) to the matching CSS system color (for example buttontext).

Using a tilde (~) prefix with any system color (for example ~ControlText) will restore the previous functionality.

This applies to the following:

• Form Controls - Any Color property (for example Background Color, Caption Color, etc.)
• User form - Background Color property.
• [color] tag used to format text presented in a form control.

The system color name will still be shown in the Property Grid, the conversion occurs automatically in the background.

Default Conversion (Hex Codes)

A System color applied to any color property or rule will be converted to a Hex Code.

The image below shows a System color applied to the Background Color property.

The table below is a full list of all available System colors and the respective Hex Code conversion value:

Enabling legacy system color conversion using tilde (~) prefix

From DriveWorks 24.1 onwards, System colors prefixed with tilde (~) will convert the System name to the matching CSS system color where possible.

Prior to DriveWorks 24.1, this was the default behavior and did not require the tilde prefix to opt-in to CSS mapping.

For example:

~ControlText will convert to the matching CSS system color buttontext.

The image below shows a System color prefixed with tilde (~) , applied to the Background Color property.

Invalid system color values prefixed with tilde (~) will be passed to the client without any conversion applied and a fallback color will be rendered.

This is the same as if they were prefixed with an exclamation mark (!).

The fallback color rendered will depend on the Control, Property and the viewer (Form Design, SOLIDWORKS Task Pane, etc.), browser or color scheme in use.

The table below is a full list of all available System colors prefixed with tilde (~) and the respective CSS mapping conversion value:

Forcing color values using exclamation mark (!) prefix (not recommended)

Color values prefixed with an exclamation mark (!) will not have any conversion value applied, and will render the raw value untouched.

For example:

!ControlText will render ControlText, rather than the hex conversion (#000000) or CSS system color (buttontext).

The image below shows a System color prefixed with an exclamation mark (!) applied to the Background Color property.

Invalid system color values prefixed with an exclamation mark (!) will be passed to the client without any conversion applied and a fallback color will be rendered.

The fallback color rendered will depend on the Control, Property and the viewer (Form Design, SOLIDWORKS Task Pane, etc.), browser or color scheme in use.

Invalid Color Values in Rules

Invalid colors in rules, for example:

="invalid"

will output as Transparent, unless prefixed with an exclamation mark (!)

Unsafe CSS Characters

Color values containing unsafe characters will have no color applied, and the viewer/browser will choose the fallback color that will render.

Characters considered unsafe are as follows:

• ; (semi-colon)
• { (open brace)
• } (close brace)
• \ (backslash)