Icon View Thread

The following is the text of the current message along with any replies.
Messages 1 to 4 of 4 total
Thread Layout suggestion
Wed, Apr 13 2016 5:03 AMPermanent Link

Matthew Jones

The auto-layout where it can be responsive is very nice, but if you
have a label and an edit, it would be perfect to be able to have the
label pulled down too, as per "widow and orphan" control. Complicated
though, I can quite understand. But labels have their "focus control"
property, so the layout engine could actually look at the previous
component when it is doing the "too wide" part, and if set to the
component in question, apply the move to that too.

Not a big priority, but would be nice.

--

Matthew Jones
Wed, Apr 13 2016 8:00 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Matthew,

<< The auto-layout where it can be responsive is very nice, but if you have a label and an edit, it would be perfect to be able to have the label pulled down too, as per "widow and orphan" control. Complicated though, I can quite understand. But labels have their "focus control" property, so the layout engine could actually look at the previous
component when it is doing the "too wide" part, and if set to the component in question, apply the move to that too. >>

If you want to do that, the best (and easiest) way would be to use a TBasicPanel, which is a *very* thin wrapper around a basic UI element in the browser, as a container for both.  This is what EWB will require in any situation to support this type of layout in a generic way.  It's how DevExpress does it, and most layout managers.

Tim Young
Elevate Software
www.elevatesoft.com
Wed, Apr 13 2016 8:05 AMPermanent Link

Matthew Jones

Tim Young [Elevate Software] wrote:

> If you want to do that, the best (and easiest) way would be to use a
> TBasicPanel,

It's what I am indeed doing, but how much nicer it could be... 8-)

--

Matthew Jones
Thu, Apr 14 2016 8:02 AMPermanent Link

Tim Young [Elevate Software]

Elevate Software, Inc.

Avatar

Email timyoung@elevatesoft.com

Matthew,

<< It's what I am indeed doing, but how much nicer it could be... 8-) >>

Yes, but that's what I'm saying: after a certain point, the additional complexity to the layout code starts to cause the *overall* layout performance to degrade to a point where it's more performant to simply use containers. "Look-backs/look-forwards are one of those things, especially if the layout order of the "siblings" is such that there are controls/elements in-between the two.

Tim Young
Elevate Software
www.elevatesoft.com
Image