Dear support,
please try to load the attached RTF document into the RichEditControl (I tested 14.2.10 and 15.1.7) to see the crash.
Regards,
Tim
Dear support,
please try to load the attached RTF document into the RichEditControl (I tested 14.2.10 and 15.1.7) to see the crash.
Regards,
Tim
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Allthough Word can open that file, I just noticed that it may be malformed RTF; in that case, however, I'd at least expect the UnhandledException-Event of RichEditControl to fire, and gracefully handle the e.Handled = true case. In other words, the RTF may fail to load, but my Application should not crash.
Hello Tim,
Yes, I have also noticed that the exception occurs on document loading. I have passed this issue to our R&D team for further research.
Please stay tuned to our updates. We will notify you as soon as we get any results.
Hello Tim,
Actually, this exception occurs because your document differs from the standard. There are four cells declared in the table row, but properties are set only for three of them. Nonetheless, it was possible to resolve it on our side and our R&D team already fixed this behavior.
Feel free to contact us if you need further assistance.