The one issue I was having with the new built in text control was resolved by registering the .dll. I did not wind up needing it anyway, but again, I want everyone to know how much I appreciate their responses!
This works fine for us on both x32 and x64 executable. We are able to see the produced html using web browser control. The whole application is based on that concept. We had some stability issues with webbrowser control, and we found that TX richtext edit v.28.0 has some issues (some times we get a garbage "a" I think it happens after udno) and we had issues with pasting images. But no problem with our application saving in html when compiled as x64.
Tx Text Control .net Crackl
In the native PB's IDE built-in TX control you would not see any TX Control registered in the O/S like you do see (as above). So IMHO, you have a "Purchased" version of the TX control. The purchased versions of the TX control have way more functionality than PB's built-in one. That would explain when you tired the save the RTE/RTF text to HTML was working before OLE wise but not using PB's built-in one. The version of the TX control Appeon gets from the vendor has less functionality than the purchased one. 2ff7e9595c
Comments