Forum Replies Created
-
AuthorPosts
-
KujoParticipant
Hello,
disable the option “MakeSkinMenu” in TsSkinProvider component (should be disabled by default).
Regards
KujoParticipantHello,
I have the same problem, but with all the dialogs; here there is an example about the PrintDialog.
KujoParticipant'Support' wrote:Thank you for the message, this error will be fixed in the nearest release.
Solved, thanks.
KujoParticipant'Support' wrote:You are right, I will check why it missing there and I will fix it.
Solved, thanks
KujoParticipantSolved, thanks
Regards
KujoParticipantSolved, thanks.
Anyway, even if I think it is not a problem but only an esthetic aspect, if the Streched property is set to True, the DialShadow and ArrowShadow are not more visible in design mode.
Regards
KujoParticipantOk, but I think is not possible to use a dialog like this:
[attachment=7339:FontDialog.png]
Regards
July 23, 2015 at 2:59 pm in reply to: SkinManager: access violation error if created at runtime #53715KujoParticipantSolved in 10.13
Thanks
July 22, 2015 at 2:50 pm in reply to: TsDecimalSpinEdit: button refresh problem when the font color changes #53704KujoParticipantSolved in 10.13.
Thanks
KujoParticipantHello,
this link downloads all the skins in a single zip file, but includes also the commercial skins: http://www.alphaskins.com/sfiles/skins/askins.zip
If you want only the free skins, simply don't use the following:
- Aluminium 2.0
- Canvas dark
- Clear sky
- SL II (not found)
Regards
KujoParticipantHello,
solved in 10.11.
Thanks
KujoParticipantHello,
solved in 10.10.
Thank you.
KujoParticipantThank you very much. :a3:
A question: when (if) you have a moment, could you check the code in attachment?
I use this code to extract the some glyphs (radiobuttons and checkboxes, including the various states and the transparency) from the skin and add they to a sAlphaImageList. This list is connected to the TVirtualStringTree in order to show the skinned radiobuttons and checkboxes (VST.CustomCheckImages and VST.CheckImageKind properties).
I'm asking this because, if you don't use anymore the ConvertMaskToAlpha function, maybe my code can be changed in a more simple solution.
Anyway, thanks again
February 14, 2015 at 10:05 pm in reply to: Skinmanager no internal skin: possible according to the demonstration, but I do not understand #53069KujoParticipantHello,
Code:procedure TForm1.Btn_ActiverClick(Sender: TObject);
begin//Form1.sSkinManager1.Active := True; // before you have to select a skin
Form1.sSkinManager1.SkinDirectory := 'C:TOUS LES THEMES';
Form1.sSkinManager1.SkinName := 'Acryl';
Form1.sSkinManager1.Active := True;
Form1.sSkinManager1.RepaintForms(True); // in XE2 it works also without thisForm1.Btn_Quitter.SetFocus;
end;
And don't forget to add the sSkinProvider component!
February 13, 2015 at 8:34 am in reply to: Skinmanager no internal skin: possible according to the demonstration, but I do not understand #53067KujoParticipantHello,
1. Load your internal skins using the “InternalSkin” property.
2. Select a skin using the “SkinName” property.
3. Save the project
Now the skin you have selected is used as default and it is always loaded when you start the program (this is true also if you use an external skin).
P.S. Please remember that the name of an internal skin is the name of the skin plus ” (internal)”, example:
External skin name: “Acryl”
Internal skin name: “Acryl (internal)”
Bye
KujoParticipant'Support' wrote:You can try this patched file now.
Problem solved, thank you.
KujoParticipantHello,
yes I have the sources.
KujoParticipantHello,
in order to activate a skin, you have to use the SkinName property:
Code:sSkinManager1.SkinName := 'Android OS (internal)';ThirdParty is used to skin, using the current skin, a component that is not included in the AC package; you can select these components using the list (as in your image) or add the components by the code, like this:
Code:sSkinManager1.ThirdLists[Ord(tpVirtualTree)].Append('TVirtualStringTree');KujoParticipantHello,
problem solved, thank you.
Now there are some warnings during the compilation:
Code:[DCC Warning] sDBDateEdit.pas(240): W1000 Symbol 'DateSeparator' is deprecated: 'Use FormatSettings.DateSeparator'
[DCC Warning] sDBCalcEdit.pas(141): W1000 Symbol 'DecimalSeparator' is deprecated: 'Use FormatSettings.DecimalSeparator'
[DCC Warning] sDBCalcEdit.pas(147): W1000 Symbol 'DecimalSeparator' is deprecated: 'Use FormatSettings.DecimalSeparator'Why you use
Code:{$IFDEF DELPHI_XE3}FormatSettings.{$ENDIF}DateSeparator
{$IFDEF DELPHI_XE3}FormatSettings.{$ENDIF}DecimalSeparatoreven if FormatSettings is supported also in Delphi XE2?
Regards
KujoParticipantHello,
can anyone help me?
Thanks
-
AuthorPosts