Re: How to get rid of constant color names for colordialog customcolors
- From: HanslH <no@xxxxx>
- Date: Tue, 24 Oct 2006 13:21:54 +0200
On 24 Oct 2006 03:51:17 -0700, "alanglloyd@xxxxxxx"
<alanglloyd@xxxxxxx> wrote:
CustColorValStr := Format('$8.8x', [ColorInt])
You pointed me in the right direction. The (almost) right formattting
string was
Format('%8x', [tKleur])
But even then if I understand this text correctly
//======================================
Hexadecimal. The argument must be an integer value. The value is
converted to a string of hexadecimal digits. If the format string
contains a precision specifier, it indicates that the resulting string
must contain at least the specified number of digits; if the value has
fewer digits, the resulting string is left-padded with zeros.
//=======================================
the string should be left padded with zeros, but it isn't. I'm left
with two spaces in front of 6 digits. Easy to correct but strange
anyway.
Rgb codes, delphi color codes, color names, color constant names,
colors as longinteger,colors as rgb hex codes .. there should be a faq
about all this :-)
.
- Follow-Ups:
- Re: How to get rid of constant color names for colordialog customcolors
- From: Maarten Wiltink
- Re: How to get rid of constant color names for colordialog customcolors
- References:
- How to get rid of constant color names for colordialog customcolors
- From: HanslH
- Re: How to get rid of constant color names for colordialog customcolors
- From: alanglloyd@xxxxxxx
- How to get rid of constant color names for colordialog customcolors
- Prev by Date: Re: How to get rid of constant color names for colordialog customcolors
- Next by Date: Re: How to get rid of constant color names for colordialog customcolors
- Previous by thread: Re: How to get rid of constant color names for colordialog customcolors
- Next by thread: Re: How to get rid of constant color names for colordialog customcolors
- Index(es):
Relevant Pages
|