Ciao Gianni,
as you rightly assume, my perplexities arise from the implementation of a functionality that relies on an OCX.
This is the creation of a form that allows you to have the main editing features of Wordpad including the integration of images.
This way you can overcome the limitation of the RichEditBox widget which unfortunately only supports text.
The development in question leans heavily on the well known RichTx32.ocx which has been available for several years.
Having almost reached the end of the implementation, I necessarily wondered how long it will be able to overcome the difficulties that could arise from the evolution of the Windows operating system.
That ActiveX control was updated way back in 2009 so maybe it's already a miracle that it still works without too many problems.
OCXs have no future and therefore it will be necessary to use other integration systems, perhaps not as simple, of the most interesting functionalities available in the form of other types of components.
Of course such difficulties do not exist within the large .NET family but we (Uniface) must try to make them understand us without too much effort, if possible.
From a technical point of view, somehow we could get almost the same integration results as the OCX, perhaps resorting to development in Java or Java-like.
But I must say that I would prefer less 'contaminated' solutions.
Regards
Luigi