search

macressler / bwapi

Automatically exported from code.google.com/p/bwapi
1 stars 0 forks source link

Drawing BW Graphics #405

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Just because we can.

DrawGraphic(int x, int y, int graphic, int frame = 0)
DrawGraphic(int x, int y, const char *pszFile, int frame = 0)

x: x position
y: y position
graphic: enumeration for graphic number, corresponding to Broodwar's Images.dat 
entries, and following those, we use "macro" id's to specify additional 
graphics like icons, cursors, and wireframes.
pszFile: The file name of the graphic file to load from the MPQ.
frame: The frame # for the graphic.

Naturally we will have our macro functions DrawGraphicMap, DrawGraphicScreen, 
etc.
We should probably come up with a macro that defines them automagically.

Internally the function will copy the grp's frame data directly to the screen 
buffer, the same way as everything else is drawn.

Original issue reported on code.google.com by AHeinerm on 12 Sep 2011 at 5:47

GoogleCodeExporter commented 9 years ago 
Another suggestion: make some Storm API available in BWAPI.

Original comment by AHeinerm on 20 Feb 2012 at 1:33

GoogleCodeExporter commented 9 years ago

Original comment by AHeinerm on 20 Feb 2012 at 1:34

GoogleCodeExporter commented 9 years ago 
The BWAPI project is slowly undergoing the migration to GitHub. All issues have 
been migrated to the GitHub issue tracker located here: 
https://github.com/bwapi/bwapi/issues

In order to receive updates on your issue, please head over to the GitHub issue 
tracker and subscribe to your issue.

Original comment by AHeinerm on 15 Apr 2014 at 7:46