What are the Activity Objects and Widths Updates for v6?

Answer

In version 6 (v6) of XMPro, a better use of the width property was enhanced filling up the real estate on the screen.

If a width for a control is specified it will honor that width and render its size accordingly; if no width is specified it will expand the control to the width of the container (column it’s in).

Prior to v6, browse pages did not have the option to size their textboxes and had a hardwired size configured in the site’s stylesheet.

There was a width and height property present on a browse page, but this was for the browse page rendering and not the main control on the form.

The introduction of a width property for a browse page to allow it to fit in better with all the rest of the controls on the screen and give greater flexibility when designing screen layouts.

The downside to this is currently when upgrading from a v5.x site you need to go through each browse control and confirm its width as it will copy the window width (if specified) to the width for the textbox control, the resulting layout can be quite interesting to view.

It was implemented in this way as it had the least core engine impact than internally rewiring all width properties.

When rendering using the default 2 columns, if an object is specified as column 0 with no column 1 specified it will span the row (currently the same behaviour as v5x), we have made it fill the row using the width property to create consistency across the forms and layouts.

All the above is controlled via the stylesheets and can be found in the ObjectTempletes for each control.

An example of the current v6 form layout: