[Properties (by Name)] [Methods (by Name)] [Events (by Name)]
Set colors for a complete palette
Source position: MUIClass.Group.pas line 272
type TMUIPalette = class(TMUIArea) |
||
protected |
||
procedure GetCreateTags(); override; |
|
Fill TagList for MUI item creation |
public |
||
constructor Create; override; |
|
Create Palette object |
procedure CreateObject; override; |
|
Create the MUI item |
property Entries: PMUI_Palette_Entry; [rw] |
|
[i] Specify the colors that the user should be able to adjust with this palette object. |
published |
||
property Groupable: Boolean; [rw] |
|
Enables/disables palette color grouping. |
property Names: TStringArray; [rw] |
|
Specify the names of a palette objects color entries. |
end; |
|
Set colors for a complete palette |
|
| | | ||
|
Super class for every other MUI class except windows and applications |
|
| | | ||
|
Subclass of TNotify to introduce the Parent relation |
|
| | | ||
|
Notify class is superclass of all other MUI classes. |
|
| | | ||
|
Base class for all MUI Class |
|
| | | ||
TObject |
Palette class generates a (big) group of objects, alltogether making up a powerful palette requester. Due to the new color selection schemes of Kickstart 3.x, you won't get a "traditional" palette requester with 2^n fields to fill in. These things really stop making sense on nice 256 or true color screens.
Instead, MUI's palette class allows defining a list of colors that the user should be able to adjust. Within a public screen manager, this would e.g. be the DrawInfo pens for a specific screen, within a terminal program maybe the eight ANSI colors.
Palette class uses a listview to let the user choose the desired color, a coloradjust object to adjust this color and a colorfield object that always shows the current color.
The user will also be able to concatenate several colors in the list, defining a single color for several entries.