Hide properties if they are not usable on this control

[DevTKSS]

Current behavior

e.g. the Background Property on a TextBlock seems to be not available but is shown in the intellisense and studio also, but if it is set, nothing happens

TextBlock.Issue.mp4

Expected behavior

In cases like this, maybe those Propertie Fields should be hidden, so the User Expirience is not disturbed from nothing happens

Which tool(s) are affected?

Hot Design™

How to reproduce it (as minimally and precisely as possible)

dotnet new unoapp -preset blank -toolkit false -tfm net9.0 -platforms desktop -presentation mvux -markup xaml -theme material -di -nav regions -log default

open Presentation\MainPage.xaml or not not really making a difference
Start Debug and enter Studio
(dont know if this is relevant: set the Style to DisplaySmall in Studio UI)
now try to change the Background Property which is presented in the Studio

Workaround

try to use those Properties and recognize they are not implemented althought they are shown

Affected platforms

Desktop (Skia)

Uno.Sdk version

5.6.37

IDE used

Visual Studio 2022

IDE version

17.13.1

Uno Platform Extension version

1.2.18

Relevant plugins

No response

Anything else we need to know?

UnoApp3.zip
Minimal Repro if needed

[nickrandolph]

This is somewhat a limitation of the XAML object model itself. Furthermore in some controls, the fact that a property isn't used may be a result of the style/control template being applied. This is great feedback and definitely something we can consider for future in terms of highlighting important/relevant properties

[DevTKSS]

Can you explain to me what do you mean by limitations of xaml?

What I would understand from it would be: its not possible to hide those if you inherit from another control?

Is that what you mean or something else?

[MartinZikmund]

Indeed it is odd that TextBlock would show a Background, such property really does not exist there 🤔

[DevTKSS]

@MartinZikmund Its also confusing and maybe at least solvable in studio ui, that we have TextAlignment and HorizontalTextAlignment available while one of them is just without functionality/change same as the background. Maybe that could be reviewed in one go?