[HeDiBo]

'Support' wrote:

Hello

Purpose of this button – using as system button in forms without titlebar

Nice

[HeDiBo]

'Stephane wrote:

it seems to work that way.

lfx.Kind.Color := $FFFFFF and slBtnGreenText;

Very nice, thank you.

This solves one part of the problem. Now getting the color right for dark skins.

[HeDiBo]

'Support' wrote:

Thank you for the demo, I will check why it happens, soon.

Also, I want to make a new TsSysButton component, which may be placed on the form client area and will emulate a system button.

The only reason I changed the system buttons is to add a hint to the close button.

What would be the extra functionality in the new emulated system button?

[HeDiBo]

'Support' wrote:

Sorry, you are right. Here is the changed unit.

Thanks

[HeDiBo]

'Support' wrote:

Yes, this code should work, but it will be great if I can find a reason of this leak.

In sPanel the allocation of BGBmp especially is a bit fishy. It is very hard to find why it is freed if the application is stopped when the bitmap is allocated.

[HeDiBo]

'Support' wrote:

Hello and thank you for the information.

I have checked GDI Plus functions, GdiplusStartup is called there in the acGDIBegin procedure.

Memory leak will be removed very soon I think, some problems with reproduction of the problem exists.

The problem is only in TsSplitView, as mentioned above. Freeing the bitmaps mentioned will solve the memory leak.

[HeDiBo]

'Support' wrote:

Hello and thank you for researching.

I will check and fix it.

I found that removing the memory leak from TsSplitView, removes the other ones too.

This change did it:

Code:

destructor TsSplitView.Destroy;
begin
FBlurData.Free;
FreeAndNil(BGBmp); (*** DB ***)
FreeAndNil(BluredBmp); (*** DB ***)
inherited;
end;

[HeDiBo]

'Support' wrote:

You are right, saving the file is not needed in this case )

Solved in 13.19

[HeDiBo]

'Support' wrote:

Some changes will be added in the nearest release.

Events will work as expected.

Solved in 13.19

[HeDiBo]

'Support' wrote:

Thank you for the project

TsRollOutPanel doesn't work with Align property, this is the reason of the problem.

I hope to improve it soon.

Thanks. I suppose you agree that it is a bug?

[HeDiBo]

No change in 13.18

[HeDiBo]

Problem solved in 13.18

[HeDiBo]

No change in 13.18

[HeDiBo]

'Support' wrote:

Thank you for the demo, I will fix it.

It works great again

[HeDiBo]

'HeDiBo' wrote:

I specifically said High and Low. Because with transparent pixels not hittable, sensitivity is Low (not absent, just lower than high sensitivity). So button is mouse sensitive always, just in different degrees.

It works. It is sufficient for my needs.

I think the property name is very silly (AllowMouseTransparency means that the mouse itself can be transparent).

Why did you not decide for MouseSensitivity being a [Low, High] selection. Believe me, that's much more descriptive.

I looked for the property in the TsFloatButton, but didn't find it. Why did you decide to give the whole group this property. It seems more related to individual buttons, isn't it?

But, again it works very well.

[HeDiBo]

The problem occurs because this change in AcAlphaHints:

Code:

procedure TacCustomHintWindow.ActivateHint(Rect: TRect; const AHint: string);
{$IFNDEF ACHINTS}
var
w, h: integer;
p: TPoint;
{$ENDIF}
begin
{$IFNDEF ACHINTS}
if Assigned(Manager) and HandleAllocated then begin // This is changed
Manager.State := hsInit;

In my case, apparently HandleAllocated is false.

[HeDiBo]

I noticed a similar behavior.

I had no idea it had anything to do with blend on moving. So, thank you for finding this.

[HeDiBo]

'Support' wrote:

Standard checkboxes shows same small rectangle.

That's why we choose AlphaControls.

'Support' wrote:

I see what you mean, but 100+ skins must be repainted for this feature.

This is a list of skins that are already OK:

Air, AlterMetro, AlterMetro2016, AlterMetro2017, Aluminium, AutumnSky (not very pronounced though), Bejing, Bejing Ext, Black Box, Blue Shadows (a bit vague), BlueGauze (also a bit vague), Blue Glass, Blue Ice, Canvas Dark (CS), Capuccino, Clean Card (somewhat vague), Clear Sky (CS), Cold (bit vague), DarkMetro, Deep (bit vague), DeepPurple, etc. (I stopped checking because so many are already OK).

So, not 100+ skins to change…

[HeDiBo]

'Support' wrote:

Maybe just do not show it if caption is empty?

Absolutely not. That's the worst method.

Have a look at the way check boxes are highlighted in Material Dark skin. You should invent such highlight for other skins too, I think.

[HeDiBo]

'Support' wrote:

Do you mean, calendar contains “d MMMM yyyy” there?

yes

[Author]

Posts