[TAZ]

Makes sense.

I looked as far back as 2 years at my project in question and it was set to true. Wish I had commented the reason.

I usually don't mess around with the color scheme that you have in place. Perhaps I was experimenting at one time and did not reset this. Don't know.

At any rate, thanks.

'Support' wrote:

This property changes system colors like clWindow, clBtnFace and others according to current skin palette.

This property may be useful if some pieces of the application has standard colors and can't be changed by other way.

[TAZ]

That was it.

By default ChangeSysColor is False. I cannot remember why I set it to True.

There are a couple of references about setting it to false fixes a problem.

Therefore, what good is ChangeSysColor?

[TAZ]

Fixed. Thanks.

[TAZ]

Just downloaded 13.4.

Red close button is added; however, it does not work.

[TAZ]

'Stephane wrote:

Standard dialogs, like MessageBox and Open File dialog, do not have close buttons when sSkinManager.DrawNonclientArea is FALSE.

They do when sSkinManager.DrawNonclientArea is TRUE.

Good observation. I did not pick up on that during my critique.

[TAZ]

'TAZ' wrote:

Thanks. Don't rush it too quickly. As always very impressed with the new features and quick fixes.

I appreciate the new feature.

Is there anyway to improve it?

When you call up the dialog or message box, the non-client area appears momentarily as skinned then it becomes non skinned. Can you prevent the dialog from showing until it has completed this operation?

Thanks.

[TAZ]

'Support' wrote:

I can't say if new stable version will be released. Big changes required in the v12 for implementing this feature.

I'm planning to publish v13 stable as soon as possible.

Thanks. Don't rush it too quickly. As always very impressed with the new features and quick fixes.

[TAZ]

'Support' wrote:

Hello

The TsSkinManager.Options.DrawNonClientArea property will be added in the v13.03

Thank you.

Is there a possibility that this could be added to version 12? With version 13 still in BETA I am always leary to use it in releases.

[TAZ]

Fixed. Thank you.

[TAZ]

Experiment. Take GetGlobalFontColor and divide or multiply it by 2 or whatever. Anything is possible.

Also look under: http://www.alphaskins.com/afaq.php Serge has some neat tips.

[TAZ]

Using what Serge suggested here is something that should help. Add it to the UpdateChartBackImage in the demo he mentioned.

Chart.LeftAxis.Title.Font.Color := GetControlColor(Chart.Parent);

Chart.BottomAxis.Title.Font.Color := GetControlColor(Chart.Parent);

Chart.LeftAxis.LabelsFont.Color := GetControlColor(Chart.Parent);

Chart.BottomAxis.LabelsFont.Color := GetControlColor(Chart.Parent);

Chart.Title.Font.Color := GetControlColor(Chart.Parent);

If you use top and/or right axis, just add them too.

Also I have done this a little differently than the demo and it works perfectly. (smMain is SkinManager)

procedure TfrmMain.UpdateChartBackImage(Chart: TChart);

begin

Chart.Color := smMain.GetGlobalColor;

Chart.LeftAxis.Title.Font.Color := smMain.GetGlobalFontColor;

Chart.BottomAxis.Title.Font.Color := smMain.GetGlobalFontColor;

Chart.LeftAxis.LabelsFont.Color := smMain.GetGlobalFontColor;

Chart.BottomAxis.LabelsFont.Color := smMain.GetGlobalFontColor;

end;

Either way should help.

[TAZ]

I can verify the flicker effect. That is interesting. It does not have focus, but it is acting like it is trying to have focus.

I tried setting the combobox style to csDropDownList. No flicker. Oh well.

[TAZ]

Sorry. I said them backwards. First is v11 and the second is v12.

[TAZ]

So I guess what you are talking about is changing the font size of the operating system instead of using the scaling mode on the skin manager.

You are missing out on the ability for the skin manager scaling mode to handle scaling instead of changing the system font size.

Look at the Skin Demo.

• Change to “Examples of components”.[*]Click on “Listview”.[*]In the title area, select 200% or any the scaling mode sizes.[*]Listview font size adjusts based on the scaling mode size.

It takes a little while to master coding for this, but the end result is great.

[TAZ]

Based on your inventory of components in your demo, the skin manager is missing?

unit Unit2;

interface

uses

Winapi.Windows, Winapi.Messages, System.SysUtils, System.Variants, System.Classes, Vcl.Graphics,

Vcl.Controls, Vcl.Forms, Vcl.Dialogs, Vcl.ExtCtrls, sPanel, Vcl.ComCtrls, sListView, sSplitter, sTreeView;

type

TForm2 = class(TForm)

sTreeView1: TsTreeView;

sSplitter1: TsSplitter;

sListView1: TsListView;

GapPanel: TsPanel;

BottomPanel: TsPanel;

private

{ Private-Deklarationen }

public

{ Public-Deklarationen }

end;

var

Form2: TForm2;

implementation

{$R *.dfm}

end.

[TAZ]

Thanks.

[TAZ]

I second that motion. Would be nice feature. Sometimes difficult to have a button that large.

[TAZ]

Based on your reply I would agree.

[TAZ]

I have added a status bar with a notification when the read edit control has focus and the notification disappears when the read edit control loses focus.

In the mean time, I tried setting the SkinData.CustomColor to true and setting the Color property to an arbitrary color. Did not work. No big deal any way. Moved on.

[TAZ]

There is one thing that puzzles me, “AllowNegative” property. It does prevent negative numbers (if unchecked) when you have a Min set to 0.

However, it will not stop Max = 0 and Min = negative problem of the Max going greater than 0. Guess you could have a “AllowPositive” property but I doubt that would be beneficial.

[Author]

Posts