1. Thierry Garrigues
  2. PowerBuilder
  3. Tuesday, 20 December 2022 09:57 AM UTC

Hi.

With PowerBuilder 2022, i use the OCX Te Edit Control v30 (https://www.subsystems.com/tewf.htm) in my application. 

I associated it with a Standard Visual of type OleControl. I am using this User Object in windows.

I also use WizSource Source Manager.

When I do a Get Latest Version on another PC, I lose the link with the OCX in my windows but not with the user object !

I must therefore for each of my windows delete the user object and put it back for it to work.

I use other OCXs with no problem.

Could someone help me?

Thank you

Thierry

Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Tuesday, 20 December 2022 17:16 PM UTC
  2. PowerBuilder
  3. # 1

Hi Thierry, did you test the TX TextControl in PB 2022 to see it really has same problems as before?  We upgraded the version of TX TextControl in PB 2022.

 

Comment
  1. Thierry Garrigues
  2. Wednesday, 21 December 2022 08:07 AM UTC
Hi Armeen

Some bugs have been fixed but other remains. I opened two support tickets with PowerBuilder 2022 : Bug 9279 and 9303

It's still very restrictive for us...

Regards
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Wednesday, 21 December 2022 16:37 PM UTC
Thanks for reporting.
  1. Helpful
There are no comments made yet.
Thierry Garrigues Accepted Answer Pending Moderation
  1. Tuesday, 20 December 2022 14:50 PM UTC
  2. PowerBuilder
  3. # 2

Hi Roland.

Thank you for your reply.

I'm not sure to understand what you mean by "I always create the OLE control as it's own object..."
Could you detail your answer ?
What is the difference with creating a Standard Visual Object of the OLE type?

For the Tx Text Control, I have problems with loss of images when converting to HTML which forced me to use Te Edit OCX.

Regards.

Thierry.

Comment
  1. Roland Smith
  2. Tuesday, 20 December 2022 15:07 PM UTC
Create a new 'Standard Visual' object, choose 'olecontrol' as the type. Then on the 'Insert Object' window, go to the 'Insert Control' tab and find your OLE control in the list and click OK. You now are in the user object painter. Save the object as 'uo_textcontrol'. Now you can place uo_textcontrol on the window objects instead of the olecontrol directly. Now you have OLE Bin data in only one object. When someone changes the window in the future, you don't have to worry about losing the OLE Bin data because it isn't part of the window object.
  1. Helpful 5
  1. Thierry Garrigues
  2. Tuesday, 20 December 2022 15:14 PM UTC
I did like that but I lose the link with the ocx...

  1. Helpful
  1. André Monz
  2. Wednesday, 21 December 2022 09:48 AM UTC
Very good advice Roland, thank you.
  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Tuesday, 20 December 2022 14:28 PM UTC
  2. PowerBuilder
  3. # 3

I always create the OLE control as it's own object and place that object on the windows. Doing that allows you to add common code to the object and there is less chance of problems like you are seeing since the OLE object would be rarely updated.

The source code of an object that is or has an OLE control will have something like this at the bottom of the exported source file:

Start of PowerBuilder Binary Data Section : Do NOT Edit
0Cuo_webbrowser.bin
2D00000a00e011cfd0e11ab1a1000000000000000000000000000000000003003e0009fffe000000060000000000000000000000010000000100000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000
1Cuo_webbrowser.bin
End of PowerBuilder Binary Data Section : No Source Expected After This Point

Somehow the binary section is getting lost. The object source and OLE bin data are stored separately in the PBL and when the IDE exports the object prior to calling the Source Control Check-In function, it appends the bin data to the source file.

Also, the RTE control built into PB 2022 is TX Text Control Version 30. You might be able to use that and no longer license it yourself.

Comment
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.