- This topic has 12 replies, 3 voices, and was last updated 4 years, 4 months ago by
.
-
Posts
-
Hello, Dick
You can look how it works in the AMegaDemo program
Additional information will be ready soon.I had a look.
The only thing I saw different is a slightly different blur. But it did not look better or worse, so that cannot be the only purpose of the FluentUI property.Are you on Windows 10
Yes
This feature works under Windows 7 also.
Dick, look the screenshot, please.
These left transparent panels were not possible in the v15.05
The FluentUI property activates it since v15.06.So, the FluentUI property should have been named SystemTransparency?
Because the current property name hints on a Microsoft Design system, which it is not. And FluentUI really hides its purpose.Maybe the name “Acrylic” would be better. As HeDiBo said, Fluent UI is a lot more than just blurred backgrounds.
Stephane Senecal
CIS Group
Delphi programmer since 2001Also, if you have no knowledge of the Microsoft Fluent architecture, the property might just as well be “TableTop”. It would be just as meaningless.
I noticed that the blur is not even the same one than the one from Fluent UI apps as Settings on Windows 10.
The blur on Fluent UI app is more pronounced. So it should not even be called Acrylic.
In the windows api, it is called Blur Behind. It’s a bit dull as a name. Maybe “SystemBlur” would be good.Stephane Senecal
CIS Group
Delphi programmer since 2001Acrylic form is a part of fluent design and I thought to make a property which will include most these parts.
After acrylic form I was planning to add more sub-properties there, but now I see that you are right, “SystemBlur” will be better. Other new properties will not be included in this property, they will be placed separately and it will be better for developer, seems, more intuitive.Acrylic blur used if Mode sub-property is “fmAcrylicBlurBehind”. It’s supported in Windows 10 only, otherwise will be used old fmBlurBehind mode.
- You must be logged in to reply to this topic.