🔒 Locked

Loading and Saving maps

Started by ImmaGNUman Sep 2, 2000 at 10:18 AM 0 replies 550+ views

Original Post

Sep 2, 2000 at 10:18 AM

ok, heres my problem. Say I have a structure like this: struct TILE_T { int foo; char bar; double baz; LPDIRECTDRAWSURFACE *bmp; } Now considering I dont want to save a DirectDraw surface to a file, should I: 1) Create a whole new struct for saving and loading with an HBITMAP instead of DDSurface? 2) Just add a pointer to an HBitmap and during the game make it 0 and use it only for saving/loading? or 3) Make it a void*, cast it to (lpdirectdrawsurface) when i use it and when i convert it cast it to hbitmap? (this sounds coolest)

Just want some input, which might give the least overhead. ----------------------------- A wise man once said "A person with half a clue is more dangerous than a person with or without one."

Steven

Sep 3, 2000 at 11:36 AM

Actually I''d stip out the LPDIRECTDRAWSURFACE *bmp (is that right? i double pointer??) and have ethier an index number for the tile or some other way to indicate the image. All 3 options you have given rely on windows re-allocating the exact same memory block each time you run your app and that these memory blocks are all pre-allocated by your system. This will never happen, unless you re-program windows and DirectX to re-allocate the blocks of memory that you want - like that''s going to happen!

The best option would be to do the following:

LPDIRECTDRAWSURFACE *IsoMaps[MAXISOIMAGES];

struct TILE_T
{
int foo;
char bar;
double baz;
int TileNum;
}

I''ve just worked out why you had the double pointer to the surface.

Topic Locked

This topic has been locked by a moderator. New replies are not allowed.