storage target. Adding them to the old XLS API would create a misleading surface: values would either be lost on save or reduced to an approximate palette color

members to the classic

storage target. Adding them to the old XLS API would create a misleading surface: values would either be lost on save or reduced to an approximate palette color ThemeColor / TintAndShade to customize palette entries lxH) and its theme-aware style propertiesle when you want to assign an RGB value. HotXLS maps that RGB value to the current workbook palette. to customize palette entries .xls 'A1'

to customize palette entries lxH) and its theme-aware style propertiesle when you want to assign an RGB value. HotXLS maps that RGB value to the current workbook palette. to customize palette entries .xls 'A1'

style concepts. to customize palette entries XLS facade does not expose those properties because a BIFF workbook has no equivalent theme/tint storage that Excel can round-trip as theme metadata

to customize palette entries Color ) and its theme-aware style properties ColorIndex 'A1' style concepts. to customize palette entries XLS facade does not expose those properties because a BIFF workbook has no equivalent theme/tint storage that Excel can round-trip as theme metadata If source code uses theme colors ) and its theme-aware style properties the target file is

or a custom palette entry. If the theme relationship must remain editable in Excel, use the XLSX facade (

ThemeColor ) and its theme-aware style properties TintAndShade 'A1' .xlsx 'D1'

] := RGB( .xls107 Color 191lxH) and its theme-aware style propertiesleX); Workbook.Worksheets[

'A1'

'D1'

Workbook.Colors[8, 0] := RGB(42, 107, 191);
Workbook.Worksheets[1].Range['A1', 'D1'].Interior.ColorIndex := 8;