Droping those components on a form and changing the font.color property from the object inspector I did not see any problem the color is shown correctly on the designer at least Lazarus 1.1 r38674 FPC 2.6.1 i386-win32-win32/win64 on win7 32bits.
The latest release of lazarus is 1.0.6 I'm using a daily build until the fpc 2.6.2 comes out and lazarus makes a release with it, I'm waiting it out.
If it is theme based as juha said then I do not think that a newer Lazarus version will help. I have themes disabled on my laptop it is not powerful enough to support them. You can disable them and test on your system to find out.
function WndCallback(Ahwnd: HWND; uMsg: UINT; wParam: WParam; lParam: LParam):LRESULT; stdcall;var hdcStatic : HDC;Begin case uMsg of WM_CTLCOLORSTATIC: Begin hdcStatic := HDC(wParam); SetTextColor(hdcStatic, RGB(23,73,107)); SetBkColor(hdcStatic, RGB(0,0,0)); result := LRESULT(GetStockObject(NULL_BRUSH)); End; End; result:=CallWindowProc(PrevWndProc,Ahwnd, uMsg, WParam, LParam);End;
I am thinking to subclass the window and override the WM_CTLCOLORSTATIC Message. But it also failed.
Strange question. Why don't you just use trunk?You can always have another stable Lazarus installed with a different primary-config-path. See the wiki articles on installing Lazarus side by side.