Re: 3 csets were pushed to core/commerce: Merge [email protected]:/var/bk/xaraya/c...

mikespub wrote:

> I haven't dived into the exact use case for this "Hidden" status
> yet, but somehow it feels in the wrong place there. After all
> we already have a property type "Hidden" too, for those fields
> you want to hide but keep functional - isn't that enough ?
>
I dont think so, the property has to be of type item id for dynamic 
objects, so the type is set. The most frequent usecase is that there 
are views and display screens of the object.
By setting it to "display only"  that solves half the situation: 
hiding it in the view screens, but it will still be visible in the 
display screens. The 'hidden' status would solve that.

I do agree however that the definition of the states (including the 
hidden) is then not using one "rule" for division and may lead to 
confusion.  I also think disable was already kind of confusing, but 
that may be me.

marcel