Forum Replies Created
-
AuthorPosts
-
March 13, 2017 at 3:03 am in reply to: How to design DevExpress grid styles or disable skin for certain classes/controls #56318zippyParticipant
I think I've found a solution. The _InitDevEx routine in acLFPainter6 gave me the clue.
If I set cxGrid.LookAndFeel.SkinName := '' during formshow event it switches the skin off and my own designed styles are used.
March 12, 2017 at 10:50 pm in reply to: How to design DevExpress grid styles or disable skin for certain classes/controls #56317zippyParticipant'Support' wrote:Hello!
Try to change the cxGrid1.LookAndFeel.NativeStyle property.
I think, that's what you need.
I think I perhaps I just need to understand better how the styles are applied to the cxGrid. When setting NativeStyle to true I lose the styling I've setup at design time.
The problem I have is at design time I have a dark colour with white text for my header, but when I run the application the grid header row appears white with black font, but I'm not sure which skin sections are relevant to the cxGrid styles. It seems my View.Styles.Header is ignored when applying the styles, although my content and footer styles seem to work.
Is it not possible to just not skin a particular control in the same way you would a standard component with the 256, -98 tag values? Bear in mind this is the older version of devexpress.
March 9, 2017 at 10:42 pm in reply to: How to design DevExpress grid styles or disable skin for certain classes/controls #56299zippyParticipant'Stephane wrote:It's 256 now or more precisely, any number that bit mask with 256 like 1000 would match (1000 and 256 = 256).
Thankyou for your help Stephane, but unfortunately this doesn't work for the DevExpress controls. As a test I placed a Tcombobox alongside a TcxCombobox and set both tags to 256. The Tcombobox is left unskinned as expected, but the TcxCombobox still has the skin applied.
zippyParticipant'Support' wrote:Hello and thank you for the demo, I will try to solve this issue in the nearest release (v11.24)
Excellent this appears to be fixed in the latest version(v11.24).
Thank you very much
-
AuthorPosts