Created on behalf of customer:
Hi … I have problem and dont know am I going something wrong in instalation progress …I use XE4 now, But … skin builder (VCL) doesnt product skin dpk for XE4. Is there my fault or have you version with corrected problem … I have too little time to prepare my apps to clients. this same problem I have using current and 13.1 version of full vcl library. So I remove them and install last (current) version … the same problem
skin builder produsts dpk up to D17 (XE3) version… not D18
The Skin Editor does not generate skin packages for RAD Studio XE4
Answers approved by DevExpress Support
created 12 years ago
(modified 12 years ago)
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
Hello,
This seems to be a bug in our Skin Editor. I have forwarded this ticket to our developers for research. Meanwhile, you can just replace all RS17 inclusions in the skin project with RS18. There should not be any problem in compiling such a project in XE4.
There is one think more…
Skin editor produces for skin an RES file. After Building and Instaling skin the second one RES file is produced that suggest, that this second is attached to project, but in fact this first is attached…
To replicate this situation you must build and install skin in Delphi using different path to bpl and dcu's. In this moment if you add skin to project and compile them you'll get an error that RES file is missing … That will be call for this first RES file produced by Skin editor…
I think, that it can be misunderstand for many of "fresh" delphi or Devexpress users.
Not sure that I understand your second question/suggestion. Would you please open a separate ticket in Support Center and describe your idea there in detail? We will consider the possibility of implementing it with future versions of our controls.
P.S.: Would you mind us publishing the content of this ticket? It can help other programmers who faced a similar problem.
Of course… if you only think, that any problem I send is helpfull for other you always can change it state to publis without my future acceptation.