I have discovered a bug in the DXL generated from a Form design element (Notes 6.5.1)
If a form contains an embedded view, and the embedded view property “Thin scrollbars” is enabled, this is not reflected in the generated XML, and when the XML is re-imported, the attribute is obviously lost.
As far as I can tell, this attribute is missing from the very definition of the dxl, since there is no attribute on the “embeddedview” XML element that could hold the information (see dtd below):
Another main attribute from embedded views, that are not represented in the DXL is the Embedded view name (the name indicated as “Name” in the first Embedded View property tab). The name attribute of the embeddedview DXL element refers to the name of the target view.
Another disturbing problem, is that when the embedded view property “Fit to window%” is selected, and the view is located in a multi-column table, the percentage (set to 100% in the embedded view property) results in XML like…
<embeddedview … widthtype=“fitwindow” width=“5040%” …>
… which, when imported, makes the embedding table unusable (column with is higher than max allowed).
I have experienced similar problems with widths of view action bars.
Problems like these, render XML processing of design elements virtually useless.
