• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • RTE Control - PowerBuilder 2017 RTF vs PowerBuilder 12.1 RTF

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (1)

Resolved RTE Control - PowerBuilder 2017 RTF vs PowerBuilder 12.1 RTF

  1. Issue
0
Votes
Undo
  1. Randolph Berry
    Randolph Berry
  2. PowerBuilder
  3. Thursday, 21 September 2017 23:42 PM UTC

We have an application coded against PowerBuilder 12.0 and 12.1 that we are trying to migrate to PowerBuilder 2017. We have a large number of documents in the RTF format from the PowerBuilder 12.1 RTE control. It appears that the PowerBuilder 2017 RTE Control produces vastly different output from the CopyRTF function on the RTE Control than was produced in PowerBuilder 12.1.

This is causing us problems because our code depends on pulling the RTF out of the RTE control and then doing various manipulations to it and then reinserting it back into the RTE Control. Because the RTF data string produced by the PowerBuilder 2017 RTE Control CopyRTF method is so different than that of PB 12.1, our code is breaking or producing garbage when it it tries to manipulate it and then reinsert it into the RTE control.

Is there any kind of a migration strategy for taking documents produced using the older RTE control and making them compatible to the new RTE control?

  1. TE Control
Powerbuilder 2017 install Support_PB.zip
Unable to Install tutorial app in Appeon Workspce ...
Responses (1)
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Thursday, 21 September 2017 23:55 PM UTC
  2. PowerBuilder
  3. # 1

Hi Randolph;

   The RTF Control is quite different "under the hood" in PB 2017 than lower versions of the PB IDE. There is an update coming to PB 2017 at the end of the month that might alieve some discrepancies. However, you should read the PB 2017 documentation carefully as it notes all the differences & nuances between the old 3rd party control and the new one.

    That being said, you can actually still use the old control with PB 2017 that Sybase first incorporated into PB v10.0. You will see a new tab page in the Application Painter that allows you to use the old control instead of the new one. So if your RTF discrepancies are too vast to use the new control, please consider using the old control for now. Especially, if your development team does not have the time to refactor your code to adjust accordingly or the output you desire is not attainable at the moment.

    Please note thtat there are more planned updates to the RTF control in PB 2017 R2 planned to be released later this year.

HTH

Regards ... Chris

 

Comment
Randolph Berry
  1. Randolph Berry
  2. Monday, 25 September 2017 22:43 PM UTC
Hi Chis,



I feel like I read somewhere (but can't find it now) that the option for the old control in the Application Painter is not available in the standard edition license, which is what we are currently using. Do you know if this is correct? If so, what license level is required for that option to become available?

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.