GpiEnableYInversion() - Revision history

Martini: Replaced content with "Moved to: [http://www.edm2.com/index.php/GpiEnableYInversion] Category:Redirects"

2017-07-17T21:46:15Z

Replaced content with "Moved to: [http://www.edm2.com/index.php/GpiEnableYInversion] Category:Redirects"

← Older revision		Revision as of 23:46, 17 July 2017
Line 1:		Line 1:
	~~Definition~~:		Moved to: [http://www.edm2.com/index.php/GpiEnableYInversion]

	~~BOOL APIENTRY GpiEnableYInversion(HPS hps, LONG lHeight);~~		[[Category:Redirects]]

	~~This function is exported by PMGPI.DLL as ordinal 723.~~
	You can use this function by loading it dynamically when needed, for example by the following code. (The code assumes that the program uses other Gpi* functions so PMGPI.DLL is already attached to the process!)

	~~static BOOL APIENTRY (*fnGpiEnableYInversion)(HPS hps, LONG lHeight) = NULL;~~

	~~void GpiEnableYInversion(HPS hps, LONG lHeight)~~
	{
	~~HMODULE hmod;~~
	~~int rc;~~

	~~if (fnGpiEnableYInversion)~~
	~~fnGpiEnableYInversion(hps, lHeight);~~
	~~else~~
	{
	~~// Interesting, it doesn't work with DosQueryModuleHandle(), even~~
	~~// though it returns the very same handle.~~
	// [ ~~rc = DosQueryModuleHandle("PMGPI", &hmod); ]~~

	~~// I have to load and free the module instead...~~
	~~rc = DosLoadModule(NULL, 0, "PMGPI", &hmod);~~
	~~if (rc!=NO_ERROR)~~
	~~return;~~
	~~DosQueryProcAddr(hmod, 723, NULL, (PFN *)&fnGpiEnableYInversion);~~
	~~DosFreeModule(hmod);~~
	~~if (fnGpiEnableYInversion)~~
	~~fnGpiEnableYInversion(hps, lHeight);~~
	}
	}

	~~Or you can tell the linker to import it, by adding something like this to your *.def file:~~

	~~IMPORTS~~
	~~GpiEnableYInversion = PMGPI.723~~


	~~Call the function with~~

	~~lHeight = height - 1;~~
	~~GpiEnableYInversion(hps, lHeight);~~


	~~Notes~~:

	I think it was introduced with the Open32 API (previously called DAPIE or DAX). It's purpose is to ease the porting of Windows applications to OS/2. Using this API for a given Presentation Space handle (HPS), all the Gpi functions will be inverted using the given lHeight value.

	Please note that not only the coordinates will be top-left based, but the blitting and handling of bitmaps will also be inverted. For example, using the GpiDrawBits() API expects a pointer to a pixel array, which is bottom-up by default. Once this call is used on the target Presentation Space, you'll have to have the pixels top-up way in your buffer if you want to have your image to be shown correctly.

	~~The current setting of Y-Inversion can be queried with the [[GpiQueryYInversion()~~]] ~~API.~~

	~~'''It seems the aptl[] parameter of GpiBitBlt does ''not'' get inverted! However, the bitmaps themselves ''do''!'''~~

	~~'''The output of GPIPartialArc gets mirrored across the Y-axis - the rotational direction changes!'''~~

ShadoW: effect on GPIPartialArc

2006-04-12T12:47:17Z

effect on GPIPartialArc

← Older revision		Revision as of 14:47, 12 April 2006
Line 53:		Line 53:

	'''It seems the aptl[] parameter of GpiBitBlt does ''not'' get inverted! However, the bitmaps themselves ''do''!'''		'''It seems the aptl[] parameter of GpiBitBlt does ''not'' get inverted! However, the bitmaps themselves ''do''!'''

			'''The output of GPIPartialArc gets mirrored across the Y-axis - the rotational direction changes!'''

ShadoW: GpiBitBlt, height - 1

2005-11-25T21:31:25Z

GpiBitBlt, height - 1

← Older revision		Revision as of 23:31, 25 November 2005
Line 36:		Line 36:
	IMPORTS		IMPORTS
	GpiEnableYInversion = PMGPI.723		GpiEnableYInversion = PMGPI.723


			Call the function with

			lHeight = height - 1;
			GpiEnableYInversion(hps, lHeight);


	Notes:		Notes:
Line 44:		Line 51:

	The current setting of Y-Inversion can be queried with the [[GpiQueryYInversion()]] API.		The current setting of Y-Inversion can be queried with the [[GpiQueryYInversion()]] API.

			'''It seems the aptl[] parameter of GpiBitBlt does ''not'' get inverted! However, the bitmaps themselves ''do''!'''

Doodle at 09:46, 10 August 2005

2005-08-10T09:46:29Z

New page

Definition:

BOOL APIENTRY GpiEnableYInversion(HPS hps, LONG lHeight);

This function is exported by PMGPI.DLL as ordinal 723.
You can use this function by loading it dynamically when needed, for example by the following code. (The code assumes that the program uses other Gpi* functions so PMGPI.DLL is already attached to the process!)

static BOOL APIENTRY (*fnGpiEnableYInversion)(HPS hps, LONG lHeight) = NULL;

void GpiEnableYInversion(HPS hps, LONG lHeight)
{
HMODULE hmod;
int rc;

if (fnGpiEnableYInversion)
fnGpiEnableYInversion(hps, lHeight);
else
{
// Interesting, it doesn't work with DosQueryModuleHandle(), even
// though it returns the very same handle.
// [ rc = DosQueryModuleHandle("PMGPI", &hmod); ]

// I have to load and free the module instead...
rc = DosLoadModule(NULL, 0, "PMGPI", &hmod);
if (rc!=NO_ERROR)
return;
DosQueryProcAddr(hmod, 723, NULL, (PFN *)&fnGpiEnableYInversion);
DosFreeModule(hmod);
if (fnGpiEnableYInversion)
fnGpiEnableYInversion(hps, lHeight);
}
}

Or you can tell the linker to import it, by adding something like this to your *.def file:

IMPORTS
GpiEnableYInversion = PMGPI.723

Notes:

I think it was introduced with the Open32 API (previously called DAPIE or DAX). It's purpose is to ease the porting of Windows applications to OS/2. Using this API for a given Presentation Space handle (HPS), all the Gpi functions will be inverted using the given lHeight value.

Please note that not only the coordinates will be top-left based, but the blitting and handling of bitmaps will also be inverted. For example, using the GpiDrawBits() API expects a pointer to a pixel array, which is bottom-up by default. Once this call is used on the target Presentation Space, you'll have to have the pixels top-up way in your buffer if you want to have your image to be shown correctly.

The current setting of Y-Inversion can be queried with the [[GpiQueryYInversion()]] API.