This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
We open the HTML editor sample project, enter the following: TextEditor.LoadHtml("<p/>"); and we get an Index out of range exception. Likewise when we try things like "<p>A</p><p>B</p> This string in the release version cause a complete lockup of the browser too. It looks like it needs some seriously simple testing before going production. We daren't use it in this state. Also, how do you clear the text? Shouldn't LoadHtml() be named AppendHtml()? How about a real LoadHtml() or at least a Clear()? Cheers, |
|
|
|
|
Hello Jason, and thanks for the feedback. We apologise for the issue with the import of a single empty paragraph. Embarrassingly, this wasn't part of our test suite. We have now added this to the test suite and fixed the issue. This fix will be in the next nightly build (19 May 2010), which you will be able to get from the Downloads page from about 1500 GMT. We haven't been able to reproduce the problem with "<p>A</p><p>B</p>" (a string similar to this is part of our test suite and is working fine). We did at one point have a bug which could cause the RichTextEditor to spin up to 100% CPU and from your comment about "lockup" I wonder if that might be the issue you're running into. This bug has since been fixed and the fix is included in the current nightly build. I've added a Clear() method to the RichTextEditor which again will be included in the 19 May nightly build. LoadHtml will now replace the contents of the editor rather than appending. Once again we're sorry that your initial experiences with the RichTextEditor have been unsatisfactory and we'll be reviewing our test suite to see if there are any other areas where our HTML import is not being adequately covered. |
|
|
|
