|
2007-07-17 11:06
|
|
|
|
AFAIK, changing the color of a button on windows can only be done if you use onwnerdrawn buttons. I don't that is worth the trouble. For now this is left open for the future and probably 'not fixable' or 'won't fix' unless somebody provides a way of changing a buttons color without making it ownerdrawn. |
|
|
I think no such thing is possible. Reading further even Qt doesn't allow this too: http://lists.trolltech.com/qt-interest/2003-07/thread01391-0.html For consistency I propose to unpublish the color property for TButton, define it should not have a color other then the default theme one and mark this as fixed (in the sense that having a published color property that doesn't work was a bug). |
|
|
TBitBtn and TSpeedButton also have the same problem. TSpeedButton is owner drawn, but themed. I'm not sure if it could have a color property. |
|
|
It's a bug in LCL and needs to be fixed! If not, it's a serious limitation on LCL's part and is not good. It is possible to do with Qt as well. Why does Kylix 3 then allow you to change the Color property? It's a published property of TControl, so all decendants should have support for it. See the attached screenshot of Kylix 3 in action. |
|
2008-02-01 08:01
|
kylix3_button_color.png (17,277 bytes) |
|
|
Kylix = qt = library that draw widgets itself Win32 = library that also has some mids about widget drawing Why LCL should invent hacks to force win32 draw color buttons? If win32 doesnot want to do that why LCL should have ability to override desinged by ms devels way of button drawing? LCL is library of native widgets = library that uses abilities of underlying libraries. If they (win32 or other) doesnot support something then LCL should not invent own ways. My opinion - this issue should be closed. |
|
|
Agree. |
|
|
@Paul Ok, so LCL uses native widgets - I get that. Well, Qt is supported widget set of LCL. So Qt should in all respects be consider 'native'. So now, because Win32 doesn't allow Button.Color, Qt may not use Button.Color either! That's a bit unfair. The LCL now limits developers only to what Win32 can do! What happened to LCL being cross-platform? What about the features of other underlying native widget sets? Is Win32 the controlling widget set for LCL. If Win32 doesn't support something, neither may the other widget sets? |
|
|
For now result file in win32 look like here: http://files.freesoft.ru/rep/672758/logox-win.exe ( http://freesoft.ru/?id=672758 ) But in CentOS it look better (like in kylix3_button): http://files.freesoft.ru/rep/672769/logox-linux-gtk-bin.zip ( http://freesoft.ru/?id=672769 ) |
|
|
Button.Color has been published. It has been marked as a restricted property in the object inspector for Carbon and win32. |
- Anonymous
