BDisp

> One challenge with this is dealing with other subviews that reference the view being "hidden". > I understand your point of view. `Visibility.HiddenFromLayout` should only affect `Dim` and not...

> There are situations where I'd like to "hide" a subview from layout. > What is the use case? As an API user I think I would just call `Remove`...

This unit test proves what I meant. In this case, I think that adding and removing a view is not the best option and in this case, let the layout...

I still think that the location is always calculated regardless of whether it is visible or not. Only the dimension will be calculated or not if it is included or...

> I don't think adding a 'hide from layout' state improves matters in this scenario. > It doesn't make sense at design time, but only at run time. > If...

This unit test pass. ```cs [Fact] [AutoInitShutdown] public void SuperView_As_DimAutoStyle_Content_With_Two_SubViews () { var supView = new View { Id = "supView", X = 5, Y = 5, Width = Auto...

This unit tests also pass. So, I think the issue is the `Border` drawing on the super-view is done before the layout calculation and only on the next `RunIteration` it's...

You can see in this images that the `AdornmentsEditor` has the height of 19, not yet deducted the current height of the `PaddingEditor` which is 1.  

> I suspect this is why I have bothered fixing it. I think I realized that once border is being drawn using subviews this will either get fixed by default...

I think it make sense to have both. `Command.Select` doesn't mean it was accepted. So, adding `Command.Accept` will mean it was confirmed and will perform some action, like closing or...