Kodigo

This preview features a DLL only solution instead of PBNI. This allows for more stable debugging and deployment. No features have been compromised from the shift. Subclassing and Application wide Hooking are featured. The first control is also demoed, a simple gradient text making use of the CustomControlBase w/c provides most control authoring needs, including theme/render services. Lacking is support for ImageList for controls, including ImageList management.

You can download here.

I migrate to 10.5 and get these compiler warnings:

kodigoGDIPlus.pbl(gdiphatchbrush).gdiphatchbrush.hatchbrush.1: Warning C0209: Function or event 'hatchbrush' must be declared before it can be compiled.
kodigoGDIPlus.pbl(gdiphatchbrush).gdiphatchbrush.destroy.1: Warning C0209: Function or event 'hatchbrush' must be declared before it can be compiled.

PB10 doesn't give this warning, must be new. The following code near the bottom of the source looks out of place to me:

on hatchbrush
call super::destroy
end on

I just checked, there is rouge code in gdipHatchBrush. I wonder how it got there? I just removed it and compiles OK. Let me know of any other weird stuff, thanks.

Are you going to convert your code from PB10 to an earlier version? PB8 would probably be far back enough.

The GDI functions that take strings are Unicode only. A conversion to an earlier version of PB would require changing the external function declarations from string to blob. Then the code would have to convert strings to unicode blobs using ToUnicode. Better to leave for someone else to tackle.

Exactly, GDI+ is unicode only, but doable. At least someone who has the need and interest can tackle it.

I tried migrating to PB11. I got an error in gdipregion that didn't really tell me what the problem was. It took awhile but I finally discovered that it does not like functions called xor. If you try creating a function by that name the IDE aborts. I changed the name of the xor functions to f_xor and remigrated. It worked after that.

Then I tried deploying as .Net Winform. I got a large number of warnings and errors. I think they could easily be corrected in PB10. I saved the messages to my website. You can see them at http://www.topwizprogramming.com/data/kodigoerrors.txt

Thanks for the heads up, Roland. I've renamed the XOR functions in gdipRegion to XOR plus parameter type (e.g. XORGraphicsPath, XORRectangle, etc.) just to avoid using "f_"

It seems that the warnings/errors on .NET deploy have something to do with structures passed as readonly arguments. I've converted the readonly arg type to value arg type. I've also stored all ToXXXXX() functions in a variable first before calling an API. You can try again on my next release if this resolves the .NET deploy issue.

BTW, I'm not sure if .NET deployment will work for the current Kodigo approach, let me know if it happens to run as I do not have PB11. Thanks again for the help!

I tried fixing some of the errors myself and came to the same conclusion. It doesn't like it when a function that returns an array is used directly as an argument to an API function.

Good idea on the XOR rename.

You can get a free personal use copy of PB11 if you join ISUG. That is what I am using.

Sybase should be giving Yeyi free copies of PB, considering all of the work he has done to truely break away from the "You can spot a PowerBuilder application from a mile away" phrase.   Something the Sybase engineers themselves could never do. 

I blame Sybase marketing way more than I blame their developers.

 And I agree, free copies of PB to yeyi!

@Roland  - OK, it's good to hear that my assumption was close. I'll do another preview some time today so you can try again. Thanks!

@Don, Grismare - LOL! Thanks for the support, guys PB11.NET deployment is still ways off from my plans, but I am hoping the DLL approach will solve that with a bonus of supporting < 10 PB versions.