I think this has to do with the MAC OS X. I've recently switched from the PC world to MAC. The symptom is that when I bring up a computed field to edit which has been saved to the .rptdesign file with multiple lines. It displays collapsed to a single line.

I can reformat during the edit session, but once it is saved again it will reload as a single line. This doesn't happen in windows using the same design file. On the MAC it happens in both 6.6 and 7.5.

To say the least, this is extremely annoying, especially if the expression is not simple. I'm surprised that there do not seem to be any other posts on this. Maybe I have something misconfigured?

e.g.

if (row["ID"] > 1250) {
"Big ID -> " + row["ID"]
} else {
"Small ID -> " + row["ID"]
}

displays as

if (row["ID"] > 1250) { "Big ID -> " + row["ID"] } else { "Small ID -> " + row["ID"] }

wbartscher,

Quote:

I can reformat during the edit session, but once it is saved again it will reload as a single line.

I just wanted a clarification here, do you mean it appears as a single line in the XML file itself or in some other wizard / UI?

Can you try changing the line delimiters in the file to Max OS? With the .rptdesign file open, select the XML Source tab, then from the File menu, select Convert Line Delimiters To and choose MacOS. If you reopen your file now, does the problem still occur?

In the xml file it appears the way it was originally entered (not as a single line) It's in the expression builder that it appears to collapse. I tried changing the line delimiters as suggested and it did not change the behavior.

One other clarification, I referred to .rptdesign files in my original post, but in fact I define my data sets in .rptlibrary files.

I've never heard back on this. The problem persists in MyEclipse 8.0/BIRT 2.5.1. I tried changing the line delimiters as suggested to no avail. Just to be clear about the issue, if you view a .rptlibrary file int the XML Source tab and scroll to the computed fields section of a data set, you can see that the expression was entered and is stored in the file with new line character(s). However, if you double click on the data set and try to edit the same computed field it appears on a single line of the expression builder (as if there were no new lines present).

I've only noticed this behavior since I started using a new Mac Book as my working platform