diff options
author | Lionel Elie Mamane <lionel@mamane.lu> | 2013-08-12 18:41:44 +0200 |
---|---|---|
committer | Lionel Elie Mamane <lionel@mamane.lu> | 2013-08-12 18:43:37 +0200 |
commit | fc92c1abebcfe9b18649d35b76bf22e001e332da (patch) | |
tree | fb864aef7414084042b5781d2aebb3f1c9c1103b | |
parent | 7382b89f354b7b7e768d2c9af73fcc7a13741702 (diff) |
fdo#67930 don't use variables for formattedtext in header/footer
I don't know why it was going through variables.
Instead, put the value where it is supposed to,
like for formattedtext in detail section.
Try it, and if something breaks, we can revert.
This also works around fdo#67930
Change-Id: Ia7f08afd8a037d3ac75676c5221ddb36aa791354
-rw-r--r-- | reportbuilder/java/org/libreoffice/report/pentaho/layoutprocessor/FormattedTextLayoutController.java | 57 |
1 files changed, 33 insertions, 24 deletions
diff --git a/reportbuilder/java/org/libreoffice/report/pentaho/layoutprocessor/FormattedTextLayoutController.java b/reportbuilder/java/org/libreoffice/report/pentaho/layoutprocessor/FormattedTextLayoutController.java index dcc153c71962..5bda08ba7900 100644 --- a/reportbuilder/java/org/libreoffice/report/pentaho/layoutprocessor/FormattedTextLayoutController.java +++ b/reportbuilder/java/org/libreoffice/report/pentaho/layoutprocessor/FormattedTextLayoutController.java @@ -100,30 +100,39 @@ public class FormattedTextLayoutController DataSourceException { final FormattedTextElement element = (FormattedTextElement) getNode(); - final VariablesCollection vc = getVariablesCollection(); - if (vc != null) - { - final String name = vc.addVariable(element); - final AttributeMap variablesGet = new AttributeMap(); - variablesGet.setAttribute(JFreeReportInfo.REPORT_NAMESPACE, - Element.TYPE_ATTRIBUTE, "variable-get"); - variablesGet.setAttribute(JFreeReportInfo.REPORT_NAMESPACE, - Element.NAMESPACE_ATTRIBUTE, OfficeNamespaces.TEXT_NS); - variablesGet.setAttribute(OfficeNamespaces.TEXT_NS, "name", name); - - final String dataStyleName = computeValueStyle(); - if (dataStyleName != null) - { - variablesGet.setAttribute(OfficeNamespaces.STYLE_NS, "data-style-name", dataStyleName); - } - - final String valueType = computeValueType(); - variablesGet.setAttribute(OfficeNamespaces.OFFICE_NS, FormatValueUtility.VALUE_TYPE, valueType); - target.startElement(variablesGet); - - target.endElement(variablesGet); - } - else + // LEM 20130812 I have absolutely no clue why it wants to go via + // a variable like that. It complicates things, is fragile + // (because the variable-set is done in *every* detail section + // again and again. This in itself is not that bad, but when + // the detail section is of height zero, the "set" us never done... + // and this whole schema fails). For now, keep the code in case + // something break. If we survive the 4.2 cycle (in its entirety) + // without regression traced to this, then remove it (for 4.4 or + // something like that). + // final VariablesCollection vc = getVariablesCollection(); + // if (vc != null) + // { + // final String name = vc.addVariable(element); + // final AttributeMap variablesGet = new AttributeMap(); + // variablesGet.setAttribute(JFreeReportInfo.REPORT_NAMESPACE, + // Element.TYPE_ATTRIBUTE, "variable-get"); + // variablesGet.setAttribute(JFreeReportInfo.REPORT_NAMESPACE, + // Element.NAMESPACE_ATTRIBUTE, OfficeNamespaces.TEXT_NS); + // variablesGet.setAttribute(OfficeNamespaces.TEXT_NS, "name", name); + + // final String dataStyleName = computeValueStyle(); + // if (dataStyleName != null) + // { + // variablesGet.setAttribute(OfficeNamespaces.STYLE_NS, "data-style-name", dataStyleName); + // } + + // final String valueType = computeValueType(); + // variablesGet.setAttribute(OfficeNamespaces.OFFICE_NS, FormatValueUtility.VALUE_TYPE, valueType); + // target.startElement(variablesGet); + + // target.endElement(variablesGet); + // } + // else { final DataFlags df = FormatValueUtility.computeDataFlag(element, getFlowController()); if (df != null) |