Forum Replies Created
-
AuthorPosts
-
Hello
I'm sorry, but Lite Edition have limitation in the list of supported controls.
Supported such standard components as TEdit, TMemo, TMaskEdit, TLabeledEdit, THotKey, TListBox, TCheckListBox, TRichEdit, TDrawGrid, TTreeView, TListView, TButton and TStatusBar.
September 13, 2010 at 8:03 am in reply to: Dramatic size increase in final exe size when skins enabled #43290Hello
Size is increased because sSkinManager is linked with most of units.
In other words, a basic part of the AlphaControls package is linked to your Exe 🙂
XPMan was added just for support of XP themes (system themes are not supported without Manifest, and AlphaSKins haven't the built-in manifest).
GeneralData, Images and Patterns properties were removed from internal skins, because are not used.
TsListBox and TsComboBoxEx controls inherited from standard controls now.
Other changes in the version 7 :
* Internal bitmap format is changed from 24 to 32 bits
* Faster drawing and improved animations
+ Added minimizing/restoring animation, added the TsSkinManager.AnimEffects.Minimizing property
+ Forms and dialogs may be alphablended automatically when moved, added TsSkinManager.AnimEffects.BlendOnMoving property
+ Added TsSkinProvider.AllowBlendOnMoving property
+ Added new cbSavedColors style for the TsColorBox component
+ Added 'SELECTION' skin section
* Drawing of selections was improved in TsListView, TsTreeView and in all comboBoxes and listboxes from the package
+ All comboBoxes and listboxes from the package may be alphablended (if defined in skin)
* Updated the ASkinEditor.exe
* All skins are updated
* TsComboBoxEx component is changed completely (default style is csExDropDown)
* In the TsButton control added support of the CommandLink style and the Reflected property
* TsSkinManager.AllowGlowing property was moved to TsSkinManager.Effects.AllowGlowing
* Huge changes in the ASkinEditor tool
* ZLibEx unit was renamed to acZLibEx for compatibility with original ZLibEx library
– Removed the deprecated TsCommonData.InitCacheBmp procedure (use InitCacheBmp procedure which is declared in the sCommonData unit)
– Support of unpacked internal skins was removed (only packed skins may be built-in now)
Some notes about a migrating from AphaControls version 6 to version 7 :
1. Don't forget to backup own projects!
2. Load all forms in projects and resave them (datamodules must be resaved too if SkinManager is placed there)
3. If you have Delphi or Builder warnings about unexisting “GeneralData” property (after the project loading) – ignore it.
GeneralData is a property of internal skin which is not used now.
4. It's strongly recommended to update all skins to latest versions (internal skins must be reloaded too).
Old skins may work slow. If you have own skin then open him in the latest ASkinEditor, press the “Warnings” button
and you will have information how the skin may be improved.
Yes, you will have this update too, of course )
I hope this component will be ready in this autumn.
Скоро буду смотреть 🙂
September 6, 2010 at 11:17 am in reply to: Letting the end user decide (saving skin settings) #43253Hello
You must insert this line
Code:ini.UpdateFile;before
Code:ini.Free;and
insert
Code:sSkinManager1.SkinName := Label1.Caption;before
Code:sSkinManager1.Active := ini.ReadBool('Settings','SkinActive',False);Hello.
XP themes must be enabled in this case (Manifest must be used). You did it?
Images are shown when AlphaSkins are not active?
Yes, implementing of this feature is in plans.
'Delphimpd' wrote:I do own the AlphaControls package or I don't?.What you mean?
Thank you John.
I will research it soon and I'll able to answer with more details.
Hello
Dialog will not be skinned if you will change the srStdDialogs will be False (you can change it before calling of dialog immediately).
What printer do you uses? I'll try to install a driver and will play with it.Ok, why you need to change the BorderStyle property to bsNone?
You will have a window which you need if this property will not be bsNone.Hello
This feature is planned only in the AlphaControls package.Hello
Please write a type of buttons – TsSpeedButton, TButton, TsBitBtn, TBitBtn or other. Small example can help.Hello
Most forms may be skinned automatically if creation and showing procedures of forms and controls are standard.
But in some cases skinning initialization may be failed. After placing the SkinProvider in design-time we have correct initialization always.
So, I suggest always to use SkinProvider where it's possible. And main form of application must have this component for initialization of animation before form showing.If you have a problem with form when SkinProvider is not used, then give me a demo please, if it's possible.
Thank you, I see glitches now and I'll try to fix it soon.
Sorry for a delay, look the answer there, please.
Hello
You can set SkinProvider.DrawNonClientArea property to False.Hello
AnimEffects.FormShow.Active property must work. You tried this property? You have only one SkinManager in the application?
I'll try to improve it soon.
Hello
Thank you for screenshots. Which HP printer you have installed?
I'll try to install drivers and I will look this dialog on my PC. -
AuthorPosts