[K.Ob]

Thank you !

That is great to hear.

[K.Ob]

Update :
I found the old versions, so i built my test with both versions 11.18 and 11.19, the result now is:
11.18 does have around 100 paints per second with one CPU core at 100%
11.19 does have 7

This is not what i remember as it was even mentioned in the emails with the support
11.18 +270 with one CPU core at 100%
11.19 exactly 10 with small variations (1 at most)

To conclude, i have something wrong in my Windows 10 and my test might not be the best case to waste time with, my observed problem is not AlphaSkins tied but more likely something with system.

[K.Ob]

Thank you HeDiBo very much !

This is very strange as mine can’t reach more than 6 on D2009, D2010, DXE5, DXE8 and Seattle, hope this will help finding and solving this issue.

Being more than 10 or less is not of important as the stable point is 10.

I searched my email archive and found when it was wrong and fixed, the version which was on my PC giving +170 was 11.18 (may be older versions too) and where fixed in v11.19 after contacting the support.
Now, i can’t find both versions to test them.

The cause of this bottleneck might be in Windows 10 Build XXXX.

About slowness : I tested two applications and i can see some parts are faster and some parts of drawing is slower this is compared to v13.18

[K.Ob]

I can confirm an abnormal behaviour that limiting the paint/repaint messages per second.

I recall that i send your support this same example in the past (may be it was version 11, 12 or 13, i can’t remember), back then the problem was the count of draw per second in the attached sample something around 170 which is too high as it should be 10, and you fixed it back then,
Now with the same example i can’t reach 10 !, it is somewhere between 5-6 when the repaint is issued, means when the paint process went the right way through SkinManager.

Hope this sample help.

Note: for you guys, if you still have older versions to test and confirm when that behavior had been changed it might narrow the problem for the Alpha team, and thank you all for your time.

Attachments:

You must be logged in to view attached files.

[K.Ob]

'Support' wrote:

But this way has some limitations and glow effect may be not defined in the current skin.

I will think how to make this feature better, I hope to publish a best solution soon.

I tried to create sample to explain what i am looking for , so here is it:

What i did is duplicating ShowGlowingIfNeeded to new function

Code:

procedure ShowGlowing(const SkinData: TsCommonData; const Clicked: boolean = False; const CtrlHandle: HWND = 0; Alpha: byte = MaxByte; DoAnimation: boolean = True; ASkinIndex: integer = -1); // DoAnimation: boolean = True; was False

This procedure code is same as ShowGlowingIfNeeded and called it from timer event like this:

Code:

var
i: Integer;
begin
sEdit1.SkinData.FMouseAbove := True;
ShowGlowing(sEdit1.SkinData);

i := 0;
while i < 100 do
begin
sleep(1);
application.ProcessMessages;
Inc(i);
end;

sEdit1.SkinData.FMouseAbove := False;
ShowGlowing(sEdit1.SkinData);

This exactly what i need to do flash control (now it is only highlight and only some skins support it ), but may be this can be a future feature as specific flash visual can be added to skins with different color than highlight.

Anyway, this snippet is wrong and should not be like that, i did this to show the required result which i think many will love to have and use, even may be this can be converted into automatic property to flash controls when changed ( edits, memo's …)

Thank you in advance and please consider to add usable interface to this visual effect.

[K.Ob]

'JM-DG' wrote:

Hi!

I would like to know if it's possible to manually trigger the highlight effect you can see when hovering your mouse over a TMemo.

I'ld like to be able to trigger it when there's a keypress instead.

Thank you for your time.

+1

Great idea and i want to add that i would love to see that highlight effect manually triggered for buttons too, ex. with a timer i can point the user to the logical button to press after filling a form (undo,cancel,…) or to point that the content had changed by triggering the effect once for a memo or a listview,

In other words please add a way to trigger the animations effect manually with a demo how to do it right .

Best regards

[K.Ob]

My problem is i already released an update and many client complaining about this, not sure if it wasn't there or i missed it.

Anyway i found a solution and most likely it is wrong but the rendering is OK with it and might be a work around for now, till support update the version and fix the right way.

Comment those lines in sListBox

Code:

procedure TsCustomListBox.CNDrawItem(var Message: TWMDrawItem);
var
…
//OldDC: hdc;
begin
…
//if SkinData.PrintDC hDC then
// OldDC := Canvas.Handle
//else
// OldDC := 0;

…
//if SkinData.PrintDC hDC then
// Canvas.Handle := OldDC;
…
end;

[K.Ob]

I have this problem too but with lbOwnerDrawVariable and really appreciate a fix, the sooner the better.

Most likely uninitialized variable somewhere, because this behavior is not consistent, and when resizing with sSplitter it start to draw fine.

[Author]

Posts