bb.donnay-software.com

hi Roger,

rdonnay wrote: ↑Mon Oct 16, 2023 5:28 am Two times I incorporated third party features into eXpress++ and both times the developer failed to support his product.
That is why I only incorporate features that are available in Xbase++ libraries.

i do not understand as i give you Source CODE of "native" Control which are well document at MSDN
the API for those 27 Windows Control exist since beginning and have never change

i have "try" to use same Name for Method and VAR to make it "compatible" to Xbase++ Control
so you need only to include DXE.CH and it should work like same Xbase++ Control ( but might have some Extra )

the "Problem" was to use Express++ DC Syntax as i never have used Express++ (shame on me)

---

even if i do not use Xbase++ any more (now harbour / HMG / Fivewin) i would always support my Work of DXE LIB
a "Problem" might be if i got a Ot4Xb "Problem" to contact Pablo to ask him.

this is why i ask if somebody, using Xbase++ v2.x, will try to convert Qt4Xb into EXTERNAL of Xbase++ v2.x

Hi Jimmy,

I got your code of RTF control you have sent to me and its great. But, I will suggest you to implement in the code all Windows API functions calls with Alaska C-API, instead of of using DllCall() and Ot4Xb library. Your code will be shorter, simpler and more consistent, the control will be faster and you will not depend on Ot4Xb library.