Display Style and Colors


Home » Support » Index of All Documentation » Wing IDE Reference Manual » Customization » User Interface Options »

By default Wing runs with native look and feel for each OS. It is possible to override this using Display Style preference. The options include using the native style, using a selected style (for example Windows while running on OS X), or using a style where foreground and background color can be selected.

Color Configuration

The colors used in the user interface are selected with the Color Palette preference. This affects editor background color and the color of markers on text such as the selection, debug run marker, caret line highlight, bookmarks, diff/merge annotations, and other configurable colors. Palettes also define 20 additional colors that appear in preferences menus that are used for selecting colors.

The defaults set by the color palette preference can be overridden on a value by value basis in preferences. For example, the Text Selection Color preference is used to change the text selection color to a value other than the one specified in the selected color palette. Each such preference allows selection of a color from the current color palette, or selection of any color from a color chooser dialog.

To set also the background color of areas other than the editor, first select a Color Palette and then set the Display Style preference to Match Palette. The foreground and background colors for the GUI will be set by the current color palette.

The colors used for syntax highlighting code in the editor are configured separately, as described in Syntax Coloring.

Add Color Palettes

Additional color palettes can be defined and stored in the palettes sub-directory of the user settings directory. This directory must be created if it does not already exist. Example palettes are included in your Wing IDE installation in resources/palettes. After adding a palette in this way, Wing must be restarted before it is available for use.

« 2.1. User Interface OptionsTable of Contents2.1.1. Windowing Policies »