Page 3 of 3

PostPosted: Jan 21, 2005 @ 5:04pm
by Kiyote

PostPosted: Jan 21, 2005 @ 5:15pm
by Johan

PostPosted: Jan 21, 2005 @ 6:29pm
by Kiyote
Thanks for the tips Johan. I'll look in to it and see if I can get it cleaned up. I'm inching ever closer to that first Beta release of the wrapper! :)

Also, perchance do you have any answers to my other questions in this thread? :oops:

PostPosted: Jan 22, 2005 @ 1:15am
by Johan

PostPosted: Jan 22, 2005 @ 1:23am
by Kiyote

PostPosted: Jan 22, 2005 @ 1:34am
by Johan

PostPosted: Jan 26, 2005 @ 1:47am
by Kiyote
Johan,

I have integrated the changes you made to return the ancestor class of the various objects. I am currently testing the ability to load a font surface and then create a font from it.

When I try to load my image with GapiBitmapFont.CreateSurface it throws an InvalidBitmap error. However, when I use a regular GapiSurface object and load it, it loads without any problems. Does the GapiBitmapFont object *require* the surface to be in bitmap format or something like that?

The file is available if anyone cares to look at it and point out what I'm doing wrong.

PostPosted: Jan 26, 2005 @ 7:25pm
by Kiyote

PostPosted: Jan 27, 2005 @ 5:33pm
by Kiyote

PostPosted: Feb 2, 2005 @ 10:24pm
by Kiyote
Well, moving on from the font problem for now... I'm curious what the implications of GapiDisplay.SurfacesAreLost returning NOVIDEOHW are. Since the application opened just fine and everything seemed to be working until I got that result...what does it mean? My assumption is that this means there is no video hardware memory or something like that? i.e - Asking if surfaces are lost when there is no video memory to lose them from is a silly question to ask it? :)

[Edit: clarify my understanding]