GapiDraw 3.5 dll for emulator

by **Guest** » Jan 12, 2005 @ 7:06am

Alright, slow progress is better than no progress I guess

by **Kiyote** » Jan 12, 2005 @ 3:04pm

by **Kiyote** » Jan 12, 2005 @ 5:02pm

Johan,

In GapiDraw.h, you have the line(193):
GDERR_FRAMETIMEOVERFLOW = ((HRESULT)0x486600f0)

Shouldn't that be 0xC86600f0?

Just wondering about the inconsistency.

by **Kiyote** » Jan 12, 2005 @ 5:30pm

Johan,

One more question for now. I don't suppose you have a list somewhere of what functions can return what error codes, do you?

ie -
Method:
CGapiSurface_CreateSurfaceFromMem
Can Return:
GDERR_OUTOFMEMORY
GDERR_INVALIDPARAMS
GDERR_INVALIDBITMAP

by **Johan** » Jan 12, 2005 @ 5:56pm

Kiyote: The first digit in the error codes describes the critical level of the return code. 4 is not an error (more of a notification), where C is an error. Values less than 0x8000 0000 are not "errors", but warnings. This is from the Microsoft DirectX standard.

The online documentation lists all possible return values for each function (CGapiSurface_CreateSurfaceFromMem is a wrapper for CGapiSurface::CreateSurface)

by **Kiyote** » Jan 12, 2005 @ 8:50pm

by **Johan** » Jan 12, 2005 @ 10:10pm

by **Kiyote** » Jan 12, 2005 @ 10:34pm

by **Johan** » Jan 12, 2005 @ 11:13pm

by **Guest** » Jan 12, 2005 @ 11:39pm

by **Kiyote** » Jan 13, 2005 @ 2:39am

GapiDraw 3.5 dll for emulator

GapiDraw 3.5 dll for emulator

Sort

Forum Description

Moderators:

Forum permissions