Here's the latest on 2.06:

I ended up running into one more issue with the auto-sizing layout functionality that delayed the beta a bit longer.  Specifically, the auto-sizing was overriding the stretching behavior, which was a breaking change that I did not want.  This is now fixed, and I'm putting together the beta over the next day or so.

My apologies for all of these delays, and especially for the insufferably long delay between minor releases.  I just never though that the auto-sizing changes would take this long to work out.

Just a heads-up: the initial beta may or may not include updated versions of the default control interfaces. It will probably only include the new "Desktop" control interfaces at first.  So, if you're on the beta list, just be sure to make backup copies of your projects and any customized control interfaces before messing around with the beta.

Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim,

> Here's the latest on 2.06:
>
> I ended up running into one more issue with the auto-sizing layout functionality that delayed the beta a bit longer.

Will the autosize functionality also include TWebbrowser?

I maded some experiments with dynamic creation of HTML code from an EWB
dataset and that works just great.
The only problem is (as we discussed before) the missing "AutoHeight".

Would be fantastic to have that.

Thanks Uli

Uli,

<< Will the autosize functionality also include TWebbrowser? >>

No.  Currently the auto-sizing is restricted to the UI elements in control interfaces, certain dialogs like message/progress dialogs, the TBasicPanel control, and various other controls like TButton with respect to certain dimensions.  For example, TButton has an AutoWidth property because auto-height doesn't make as much sense with a button.

I *will* however be expanding the usage of the auto-sizing as things progress, moving it into forms/panels and other controls, where necessary.  It has to be done carefully, though, because sometimes there are embedded UI elements in the control that need to mirror the auto-sizing of the control's outer base element.  For example, a TPanel needs to have both its outer base element and its client element using the same auto-sizing setup, otherwise the auto-sizing won't work.

As for the TBrowser - I think a better option would be to move forward with what we previously discussed regarding embedded HTML, and just have that implementation surface some auto-sizing properties.

Tim Young
Elevate Software
www.elevatesoft.com

Tim,

thanks for this detailed explanation.
Looking forward to the autosize functionality - that will be a great
improvement.

> As for the TBrowser - I think a better option would be to move forward with what we previously discussed regarding embedded HTML, and just have that implementation surface some auto-sizing properties.

OK. Embedded HTML sounds excellent - can't wait to use it in my
applications.

Uli