- This topic has 5 replies, 3 voices, and was last updated 10 years, 4 months ago by HeDiBo.
-
AuthorPosts
-
June 8, 2010 at 10:45 am #33803SriParticipant
In a simple format can someone explain to me how to use Devexpress Quatum Grisd with alpha controls please.
Step by step instruction please.
Thank you in advance
Sri
June 13, 2010 at 5:34 am #42759SupportKeymaster1. Install DevExpress and AlphaControls
2. Enable the 'DEVEX' key in the sDefs.inc file (AlphaControls), must be {$DEFINE DEVEX}
3. Be sure that latest version of DevExpress is installed, or check a list of supported DevExpress versions in the beginning of the acLFPainter.pas file (AlphaControls)
4. Configure the sSkinManager component and compile the project.In the run-time will be skinned all DevExpress controls which have LookAndFeel property properly supported. LookAndFeel.NativeStyle property must be False.
July 15, 2014 at 12:20 pm #52200HeDiBoParticipant'Support' wrote:3. Be sure that latest version of DevExpress is installed, or check a list of supported DevExpress versions in the beginning of the acLFPainter.pas file (AlphaControls)
Hi Serge,
I have DevExpress 2011.2.9
At the top of acLFPainter i find:
Code:{$DEFINE VER14_1_2} // cxGrid version 14.1.2 and newer
{$DEFINE VER13_2_2}
{$DEFINE VER12_2_3}
{$DEFINE VER12_1_6}
{$DEFINE VER26}
{$DEFINE VER23}
{$DEFINE VER653}
{$DEFINE VER650}
{$DEFINE VER645}
{$DEFINE VER640}Which of these defines must be kept and which must be hidden. Or where can I find the versions that the module tests?
July 15, 2014 at 1:21 pm #52202HeDiBoParticipant'HeDiBo' wrote:Which of these defines must be kept and which must be hidden. Or where can I find the versions that the module tests?
By trial and error, I found that for version 2011.2.9 the following combination of defines is needed:
Code://{$DEFINE VER14_1_2} // cxGrid version 14.1.2 and newer
//{$DEFINE VER13_2_2}
//{$DEFINE VER12_2_3}
{$DEFINE VER12_1_6}
//{$DEFINE VER26}
{$DEFINE VER23}
{$DEFINE VER653}
//{$DEFINE VER650}
//{$DEFINE VER645}
//{$DEFINE VER640}That's no way obvious is it? Those version numbers don't make any sense. Or what do I not see?
Regards ;-}
Dick
July 15, 2014 at 3:07 pm #52208SupportKeymasterThis list of keys used for different versions of DevExpress package, because changes in declarations exists there.
July 15, 2014 at 7:14 pm #52215HeDiBoParticipant'Support' wrote:This list of keys used for different versions of DevExpress package, because changes in declarations exists there.
I already understood that.
But look at the definitions that were needed to get it to work with DevExpress 2011.2.9.0:
Code:{$DEFINE VER12_1_6}
{$DEFINE VER23}
{$DEFINE VER653}That list can only be made by trial and error. There's no logic in it. There must be a better way.:eek:
-
AuthorPosts
- You must be logged in to reply to this topic.