guys,
I downloaded the sample app for the richtexteditor in the grid. If the column is a reguar part of the grid, it works flawlessly, but the second I make it a preview row column, i get the rtf code view. Any suggestions?
See pictures below that show the same field (one as regular column, other as preview colum) that are rendered differently.
I am using 10.2 and the latest service release. Heavy on the app stlying
Hey
I'm not certain but I don't think the AutoPreviewField column uses embeddable editors, so that would preclude the use of the RichTextEmbeddableEditor therein. Incidentally, we consider that approach to be obsolete as we have since added a control to our suite, UltraFormattedTextEditor, which is a native .NET replacement for the RichTextBox control. However, if I am correct about the AutoPreviewField column not using embeddable editors, I'm afraid this information doesn't help you, since the UltraFormattedTextEditor provides an embeddable editor to the column.
ah... so does the formatted text editor support rich text? I thought it was a proprietary markup language.
Hello,
I am just checking about the progress of this issue. Did you solve your issue accordingly to the information that Mike provided you? Let me know if you need any further assistance.
Thank you for using Infragistics Components.
Well, you could write a converter to translate our customer XML into RTF (which is supported in the Documents engine via the AddRichContent method). Or you could write code to convert the XML into a document directly.
But there is no automatic export or convert functionality for either of these cases.
No, you had me right the first time. I am building a report writer. So, I cannot use your ultraRichTextEditor to build the components of a report using the document engine?
Oh... I think I may have misunderstood your question.
If you have FormattedText in a cell of the grid and you export that grid to a document (PDF/XPS) then yes, the grid document exporter will convert that XML into something the document can handle and preserve the formatting.
If I recall correctly, we decided to go with our own custom XML format because RichText was simply too massive (and rich) to support in it's entirety. And also, we needed to provide certain functionality that RichText could not. For example, we wanted to give developers the ability to respond to clicks on links that were not necessarily valid URLs and show a dialog or perform some other action.
vbhandyman said:am i correct in assuming that your rich text editor control works with your document object?
Actually, no. The Documents engine doesn't have any built-in conversion from the FormattedText xml. There is a sample, however, which provides code to import Rich Text into a document.