Text Area v RTF area how to get carriage returns viewable

A bit of a strange connundrum.

I have a text area and i want to see and be able to edit its contents.

So RTF seems to be the best solution as it wraps text so i can see all of my data that has been stored in the field.

If i build the field data from other fields using a method and then view that in another layout (my report preview) having used a display tag to get it their, it ignores all the carriage returns.

If i go into the field and add one character, then go back to my preview screen it has then recognised the CRs.

Looking at the back end database, it appears that the text in the field is not converted to RTF until i have done some manual input into the fields element rather than the automatic work i have done in my script to populate the dataprovider to that field.

I suppose the question is:

  1. is there any way of getting a text_area to wrap text?

  2. is there any way of forcing the rtf element field to convert its contents to RTF through a method as simply populating the dataprovider field doesnt seem to do this.

David

Not sure but isn’t it so that disabling the horizontal scrollbars makes the text wrap in a (normal) text area?

Interesting,

Another useful tip, which i would have never guessed.

It actually causes a more interesting problem, in that to use a nicely formatted approach i have created a report template field in which the only way i can have varying text styles is using RTF, so although your answer solved one problem, i then found setting that back to plain text area wouldnt allow me to have bolded headings with slightly smaller %%inserted section%%.

So i am grateful for the information as i couldnt have guessed that in a million years of playing around, but actually using the rtf route, and then selecting and pasting does actually seem to get over the problem of getting the rtf stored in the database field without having to upset the field by adding and deleting one character.

Thanks again

David