There’s no real bug, the ForceHiddenPropertyVisibility flag is doing what it’s supposed to, it’s just that if you want to only show properties that are marked as InstanceEditable (in BP) or EditAnywhere (native), you can’t.
Based on some quick testing in editor:
-
Every Property created in Blueprint has CPF_Edit regardless of their other flags.
-
When a BP property is marked as InstanceEditable, it loses the CPF_DisableEditOnInstance flag (which seems to be a flag specific to Blueprint properties)
Personally I think it would be nice to change the ForceHiddenPropertyVisibility flag into an enum where you have:
-
Show everything
-
Current ForceHiddenPropertyVisibility=true
-
Show properties with CPF_Edit
-
Current ForceHiddenPropertyVisibility=false
-
Show only instance editable properties
-
BP: CPF_Edit && !CPF_DisableEditOnInstance
-
Native: Whatever CPF_Edit + EditAnywhere is. Not sure what combination of flags represents an EditAnywhere native property.
I just don’t see the DetailView in its current form being that useful unless you use it only on classes where everything is fully exposed (BP InstanceEditable or native EditAnywhere), because you can’t actually change those non-exposed properties if you click on them in the DetailView widget from my experience.
For example, with these 3 Blueprint properties in a UMG DetailView with ForceHiddenPropertyVisibility=false, I see all 3 properties but only the first one can be changed. The other 2 just don’t respond and I have no way of hiding them without moving them into a different category and starting to whitelist the categories instead of showing all properties.
