1. Pierre DETE
  2. PowerBuilder
  3. Friday, 08 November 2019

Hi all PB users,

 

We are facing an issue with RichtextEdit Control.

Application ->Additional Properties -> RichTextEdit is set to 'Built-in Rich Edit Control'.

With this configuration we are not able to capture '~' (tilde) car in rte control.

If we change Application ->Additional Properties -> RichTextEdit to 'Built-in TX text control' '~' car is available but there is big bug with SelectText and ReplaceText which don't have the same behavior with end of line string (~r~n).

For now, we don't have the solution ...

All that seems arrived with PB2017.

 

Pierre

 

Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Pierre;

     Yes, I reviewed a related ticket # 3614. I was able to replicate that RTE issue using the TX control. Swapping over to the TE Control though fixed that behavioral issue (not sure if you tried that). However, the TE control also has its Pro's & Con's vs the TX control in its slight behavioral differences. So you'll have to think about this & carefully test your App(s) if you do switch RTE handlers.

     I also tested the example code in PB2019GA and found that using the TE control worked OK with the Test Case I was supplied with. However to my surprise, the TX control option in PB2019 even behaved differently than PB2017R3 using the same PowerScript code.    :-(

     However, this does point out that there are some minor TX control behavioral differences between PB2017R3 vs PB2019 even though theoretically, they should be the same control under-the-hood. My guess is that the behavioral changes might be around the PB "Wrapper" used to interface with the TX control. This ticket has now been transferred to Engineering for a closer look.

    Please create a Support Ticket for your RTE issue as well so that Appeon can address these subtle issues around the TX control ASAP.

Regards ... Chris

 

Comment
There are no comments made yet.
  1. Wednesday, 13 November 2019
  2. PowerBuilder
  3. # 1
Pierre DETE Accepted Answer Pending Moderation
0
Votes
Undo

Hello,

As I said removing all the ReplaceText to use the TX Text control mode is very much more annoying for us than the  ~ problem.

For now we stay in Buitl In mode and we manage the ~ by catching the key press :

ELSEIF KeyDown(Keycontrol!) THEN
  IF KeyDown(key2!) THEN
      rte_1.ReplaceText("~~")
  END IF

But we are hoping for a stable version of RichTextedit.

Regards Pierre.

Comment
But that's a solution that might not always work:

What if I copy some text from Word or from an email or a webpage and then paste it into the RTE? There goes your key event ...

If you really need this to work: Export the text in richtext format or text format to disk. Open that exported file, FileReadEx and replace whatever you have to replace.

I do have an initial version on codeXchange called "richerText" which is a rte made in .Net. It's not perfect yet though, but gives you full control. Let me know if you have time to work with that possible alternative solution until everything is stable with the RTE (maybe 2 years I guess).



Just an idea,

regards,

Miguel
  1. Miguel Leeuwe
  2. Tuesday, 12 November 2019
I Miguel,

There is no problem with copy/past, ~ can also be captured by ALT-126. There is only a strange behavior with key ~ which do nothing, in french keyboard it's ALT Gr + 2.

For now the keydown solution is working and will be shortly delivered to our customer.

Regards,
  1. Pierre DETE
  2. Wednesday, 13 November 2019
There are no comments made yet.
  1. Tuesday, 12 November 2019
  2. PowerBuilder
  3. # 2
Pierre DETE Accepted Answer Pending Moderation
0
Votes
Undo

I Armeen the richtextedit in Tx text control mode has no problem with the '~'. It's a Built Rich Text mode issue, but for now I can't see how we can use Tx Text mode as the ReplaceText is not working properly.

Regards Pierre.

Comment
Please open a bug for this so we can get it fixed. Thanks!
  1. Armeen Mazda
  2. Tuesday, 12 November 2019
Hi Armeen,

The bug

https://www.appeon.com/standardsupport/search/view?id=2723

already describe the problem.



Regards

Pierre
  1. Pierre DETE
  2. Tuesday, 12 November 2019
There are no comments made yet.
  1. Tuesday, 12 November 2019
  2. PowerBuilder
  3. # 3
Armeen Mazda Accepted Answer Pending Moderation
0
Votes
Undo

Hi Pierre, Please open a support ticket.  In PowerBuilder 2019 R3 there will be a new version of Text Control that supports more features and 64-bit.  We would like to do our best to work with Text Control vendor to get any important bugs fixed since 2019 R3 is our long-term support (LTS) version.  Thanks.

Comment
There are no comments made yet.
  1. Friday, 8 November 2019
  2. PowerBuilder
  3. # 4
Pierre DETE Accepted Answer Pending Moderation
0
Votes
Undo

Hi Chris,

 

We have another problem with TX control, ReplaceText is not working. It truncs some characters if you have ~r~n end of line sequence in the Richtextedit.

Pierre

Comment
FYI:

If you use the "build in TX text control", the one that's supposed to solve our problems, "SelectedText()" does a similar truncation. This bug has been reported by several people and was supposed to have been solved in 2019, but it's not.
  1. Miguel Leeuwe
  2. Sunday, 10 November 2019
Correction: It HAS been resolved in 2019 GA, but came back in PB 2019 R2 beta. Hence my previous (incorrect) comment.
  1. Miguel Leeuwe
  2. Tuesday, 12 November 2019
Here's a link if you're interested, I really have to dedicate some time these coming two weeks to make it a bit better:

https://community.appeon.com/index.php/qna/q-a/outlook-email-using-richertext-activex/oldest#filter-sort

  1. Miguel Leeuwe
  2. Tuesday, 12 November 2019
There are no comments made yet.
  1. Friday, 8 November 2019
  2. PowerBuilder
  3. # 5
Chris Pollach Accepted Answer Pending Moderation
0
Votes
Undo

Hi Pierre;

   If you are using PB2017 R3, then please try the TX Control instead of the "Built-in Richtext" (which is the TE Control) by changing this setting in your Application object's App Painter. See if that helps.

Regards ... Chris

 

Comment
Hi Chris, this is the reason why I started to write my own RTE. Pierre says that the 'old' rte has a problem with changed return characters behaviour.

I would paste a link to mine, but it's not perfect yet. Maybe next week.
  1. Miguel Leeuwe
  2. Friday, 8 November 2019
There are no comments made yet.
  1. Friday, 8 November 2019
  2. PowerBuilder
  3. # 6
  • Page :
  • 1


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