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

Resolved RTE - Newer one or TxText Control ?

  1. Advice
1
Votes
Undo
  1. Sivaprakash BKR
    Sivaprakash BKR
  2. PowerBuilder
  3. Saturday, 16 November 2019 11:24 AM UTC

Hello,

Do we have a clear idea of what Appeon is going to do with RTE control is concerned.   At one point we heard that they plan to develop the in built newer version of RTE further and now, with 2019R2 release, we hear that 64 bit TX Text control is introduced.  

Would like to hear which one we should use ?  

Is the inbuilt will be focus of Appeon or the old TX Text control will be the focus ?
If old one is reviewed, will it get updated with the latest (or later) version of official TX Text control ? 
What Appeon planning with RTE ?

If both will be there, can we have an option to select one at window / control level ?  That we can try and implement the one that's best fit for that window.   Currently it's available at global level only, I think. (till 2017 R3).

Since my next developments consists of good number of RTE, I would like to hear from experts and Appeon, which one will be better.

Happiness Always
BKR Sivaprakash

 

  1. PowerBuilder (Appeon)
PB 2019 - missing context menu
Appeon Connection with Sybase database
Accepted Answer
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Saturday, 16 November 2019 14:45 PM UTC
  2. PowerBuilder
  3. # Permalink

Use TX Text Control please!  

Most likely 64-bit version will be available in PowerBuilder 2019 R3.

Comment
Load more comments
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 18 November 2019 14:58 PM UTC
Yes, this is our plan for PowerBuilder 2019 R3.
  1. Helpful
Miguel Leeuwe
  1. Miguel Leeuwe
  2. Thursday, 21 November 2019 08:19 AM UTC
Thank you Armeen, but ... R3, that's quite far away. People might need a fix for SelectedText() right now. The workaround of using the clipboard is not valid for all scenarios.
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 21 November 2019 10:02 AM UTC
I'm not saying you have to wait until R3. It is possible we will fix in a maintenance release (MR). I'm just saying that we definitely want to fix this by R3 at latest since we plan to make R3 the long-term support version of PowerBuilder. If a support ticket is not already created for the SelectedText() issue, please create. Thanks.
  1. Helpful
There are no comments made yet.
Responses (4)
Ricardo Colarina
Ricardo Colarina Accepted Answer Pending Moderation
  1. Thursday, 28 November 2019 02:29 AM UTC
  2. PowerBuilder
  3. # 1

Hi Armeen,

Thanks again for your response.  However you still haven't answered if the built-in (new) RTE reported bugs are still going to be fixed, like the the issue with wrong font.  Maybe I need to ask the question outside of this thread?  As I mentioned previously, using TX Text Control, the window with a datawindow with an RTE column freezes.  I reverted to a previous version of our application without any of the (new) RTE stuff I coded, changed the datawindow column edit style to a richtext from edit, and the window doesn't crash.  However, scrolling through the rows is very slow.  The window in general is slow, and the hyperlinks doesn't work. 

The new RTE control has addressed a lot of the earlier reported bugs, most especially the some of the performance issues, which is great.  Actually, apart from the incorrect font when adding at the start of an existing text, the RTE control is really good, with a few workarounds.  Our organization have been wanting the hyperlinks functionality for awhile, and when it was added in the new RTE control in PB 2017, we were happy.  We have functioning editable hyperlinks (with optionally different "text to display") in texts in both the datawindow and an associated popup window with hyperlink tooltips.  So now I'm worried that the remaining built-in RTE bugs won't be fixed, worst still the control be discontinued.  And that with Bug 2991 in TX Text Control treating the hyperlinks (non)functionality as a new requirement/enhancement rather than a bug.

I will continue testing the TX Text Control when I get some extra time and log bugs, but initial results doesn't look good (the buggy early versions of the new RTE control worked a lot better).  Can you please address my concerns.

Thanks.

Best Regards,

Ricardo

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 28 November 2019 07:00 AM UTC
If a feature is deprecated then we will no longer fix bugs. We haven't announced officially that TE Edit control is deprecated so that is why I wasn't directly addressing your question head on, but I was still trying to nudge you in the direction we think we will head.

Most our customers have quite the opposite experience... they feel the TX Text Control is much more stable. After all, it is the same time-tested RTE that was in PB 12.x for almost a decade. We are aware of a few regression bugs that may be related to the integration code layer. We would most like address these some in 2019 R2 and remainder important ones in 2019 R3.

Anyway, I highly recommend that you test with PB 2019's TX Text control that is built in and open as many bugs as you find so we can address as many as possible in the upcoming 2019 R2 and R3.
  1. Helpful
There are no comments made yet.
Ricardo Colarina
Ricardo Colarina Accepted Answer Pending Moderation
  1. Monday, 25 November 2019 00:48 AM UTC
  2. PowerBuilder
  3. # 2

Hi Armeen,

When you say "you want TX Text Control to be the RTE we standardize on for the long-term", will the bugs reported for the Built-In Rich Text control be fixed by then?  As I mentioned in my first response to this thread, I've got editable hyperlinks functionality, including tooltips working using the Built-In Rich Text control.  And it is working fine, apart from issues I cannot provide sufficient workarounds for, like the incorrect fonts.

I tried the TX Text Control and did a full build in PB 2019 in Windows 2012 R2, but the window that has the richtext column freezes upon opening, and the wait chain points to splwow64.  And speaking of hyperlinks, I found Bug 2991 and it is to do with hyperlinks not working in the TX Text Control.  It was indicated that it should be a new requirement/enhancement rather than a bug.  I don't agree that this is not a bug as hyperlinks should be able to be added and edited in richtext controls and it is working in the Built-In Rich Text control.  If you will be standardizing TX Text Control then shouldn't hyperlinks be fully supported in it?

Thanks.

Best regards,

Ricardo

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Monday, 25 November 2019 22:02 PM UTC
Hi Ricardo, Assuming everything goes as planned we would be recommending to set the configuration to use TX Text Control engine instead of TE Edit control engine. Under this situation, we would be fixing bugs with the help of the vendor in the TX Text Control instead of TE Edit control. So I recommend testing the TX Text Control now, and any important bugs you find please open support tickets so we can try to address in PowerBuilder 2019 R3, which will be our next long-term support version.
  1. Helpful
There are no comments made yet.
Ricardo Colarina
Ricardo Colarina Accepted Answer Pending Moderation
  1. Thursday, 21 November 2019 02:28 AM UTC
  2. PowerBuilder
  3. # 3

Hi All,

Does anyone know if the built-in RTE reported bugs are still going to be fixed, like the the issue with wrong fonts?  I have a window with a datawindow with an RTE column and another window with an RTE control.  The richtext is to allow users to add functioning hyperlinks, including tooltips.  I've got workarounds for most of the bugs and performance issues and the functionality is working well enough.  This is using PB 2017 R3 build 1858 in Windows 8.1.

I tried using the TX Text Control in PB 2019, then did a full build.  But upon opening the window with the RTE column the application freezes then eventually crashes.  I did this in a Windows 2012 R2 VM.  I still haven't spent much time finding out what exactly causes the application to crash but I'm hoping someone may have an idea.

Cheers.

Ricardo

 

Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 21 November 2019 07:20 AM UTC
Hi Ricardo, please open bugs for TX Text Control in the support portal so that we can get any remaining issues resolved in PB 2019 R3. PB 2019 R3 is targeted to be a long-term support version, and we want TX Text Control to be the RTE we standardize on for the long-term.
  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.
We use cookies which are necessary for the proper functioning of our websites. We also use cookies to analyze our traffic, improve your experience and provide social media features. If you continue to use this site, you consent to our use of cookies.