Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
30
Hex 0x1F from UltraTextEditor – how come?
posted

I have a WinForm application and I use UltraTextEditor for text input. Further on, the application saves the entered text, together with a lot of other inputs, in a text file formatted with xml. Sometimes, really rarely but still, hex 0x1F ends up as a value between the tags in the xml-file that would surround the value entered via UltraTextEditor. When this happened it was always just hex 0x1F between the tags, no other character and always multiple occurrences. Sometimes only 2, sometimes up to 6 hex 0x1F in a row.

When my application would then read this text file and make an xml document from the text, hex 0x1F causes an error, because it is an invalid character in xml. I don't know how these characters could land in the UltraTextEditor, but they have to come from there, there is no other way in the application through which the value that ends up between the xml-tags would be delivered. It has to come from the Text property of the UltraTextEditor instance that I have in my application.

The question is how the character can come into UltraTextEditor. How can you enter that character? Is there a key combination that accomplishes this? When there are always multiple occurrences of it when it occurs, I think it is about some repeated input, which is not visible in the control for the user, after which the input is stopped.

Does anyone know how to input hex 0x1F into UltraTextEditor? Does anyone know of a situation where the control for some reason itself generates this value and then delivers it via its Text property?

Thanks for any suggestions, as I am completely confused about this.

Parents
No Data
Reply
  • 7535
    Offline posted

    Hello Alfons,

    Since this is a duplicate with the private case C-00233297 you created , you may close one case and can continue with the other one to avoid duplicate responses.

Children
No Data