Microsoft® Windows® GDI+ exposes a flat application programming interface (API) that consists of about 600 functions implemented in Gdiplus.dll.
C:\Program Files\Common Files\Microsoft Shared\VFP\gdiplus.dll
Check if you have the latest version of gdiplus library installed.
For C++ developers the functions in the GDI+ flat API are wrapped in about 40 C++ classes. Visual FoxPro developers are not able to instantiate any such class in pure FoxPro code. That is why the flat API makes a good choice.
July 5, 2004: Visual FoxPro 9 presents new property GdiPlusGraphics. My understanding is that this property is applicable to the ReportListener and probably to the _SCREEN and FoxPro Form objects.
Recommended reading:
Articles of Markus Egger.
The Basics of GDI+
Using GDI+ in ASP.NET Web Applications, Part 1
Using GDI+ in ASP.NET Web Applications, Part 2
Using GDI+ in the VFP 9 Report Writer by Christof Wollenhaupt published in July 2004 issue of FoxPro Advisor.
Get to Know .NET GDI+ by Ken Getz published in March 2003 issue of FoxPro Advisor.
* * *
There is another GDI+ class written by Alexander Golovlev that you can find in UniversalThread download section. This class is freeware and contains lot of useful functionality.
* * *
Aug.04, 2004: GDI+ Foundation Class to be shipped with VFP9 final release. Read Using GDI+ in VFP 9.0 with the FFC Library, Part 1 article in Fox Talk.
Finally it is shipped on August 6, 2004.
* * *
BINTOC() accepts new parameter in VFP9: bintoc(m.tW,"F") -- conversion to 32-bit float format. That probably makes conversion routines Int2Float and Float2Int in the code above obsolete.
* * *
May 10, 2006: Names of properties of RECT class have been changed from (Left, Top, Width, Height) to (rleft, rtop, rwidth, rheight). RECTF, a subclass of RECT, could not properly access the methods of the parent class because of those risky names.
* * *
May 19, 2006: Errors may occur when moving, deleting or copying graphics files that have been used recently for creating GDI+ objects. Most likely those objects still exist in memory and must be released to enable file operations. This is in a way similar to VFP CLEAR RESOURCES command not clearing cached bitmap file if it is still used in Picture property.
|