- Josh Turner
- PowerBuilder
- Wednesday, 31 January 2018 07:04 PM UTC
If you use rich text in your applications and are on 12.X and are thinking about upgrading to 2017, I would seriously reconsider. The regression bugs introduced with the built-in rich text control are bad enough to render the control useless for us. If you store rich text in the database and use a datawindow with the rich text edit style column to retrieve the data, beware. Setting the column to auto-size height will create an unacceptable amount of variable white space beneath the text upon retrieval. What's really shocking is that it took very little time and effort to produce the problem and I'm not sure how it wasn't caught. The suggested work-around from Appeon was to spend several thousand dollars to buy the old TX Text Control and integrate it into our application. We did. Unfortunately, we're still unable to get our datawindows to display as they did in 12.6 and prior using the old control. While the performance issues were resolved with the old control, the variable white space below the text was still and issue (though not as severe). We are extremely disappointed in these bugs and with no work-around available we will be forced to go back to a previous version of PowerBuilder, with no return on our investment in PowerBuilder 2017 or the TX Text Control we were told to buy. We cannot wait another 6 months for a fix.
And, yes, I've already downloaded and installed R2 without any change in behavior. Frankly I'm surprised to see the performance issues for the built-in rich text editor were not addressed in R2 since that has been a known issue for some time. Also note that the R2 Release notes known issues does not include the issue above. Let it be known.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.