summaryrefslogtreecommitdiff
path: root/src/mesa/drivers/windows/gdi/wmesa.c
AgeCommit message (Collapse)Author
2007-08-23For _mesa_share_state(), update the context's references to the new share ↵Brian
group's objects (Shane Blackett)
2007-07-21Fix a number of MINGW32 issuesZhang
2007-06-28a variety of fixes for MingWzhang
2007-04-26enable 2.1 extensionsBrian
2007-04-24assorted fixes for Windows/VC8Karl Schultz
2007-02-16Commiting a few minor fixes to glut fbdev (segfault on a separate stack)Sean D'Epagnier
Updated all drivers that used the old _ac_ functions to use the new _vbo_ functions. I know this fixed the fbdev driver, it looks like it might fix some other drivers too.
2006-11-01Remove x/y/width/height parameters from Clear functions.Brian Paul
2006-10-21don't use params passed to Clear()Brian Paul
2006-08-30Handle API and dispatch table changes that removed a bunch of extension ↵Karl Schultz
entry points.
2006-07-21check for non-nill pwc in WMesaMakeCurrent(), bug 7585Brian Paul
2006-04-03Fix problem reported by Bill Newman in read_rgba_pixels for 16 and 32 bit ↵Karl Schultz
(GDI driver). Bug would cause the wrong pixel to be read if more than one pixel requested and could cause memory access violations.
2006-03-30Clean up data structures, finishing off some of the cleanup work suggested ↵Karl Schultz
by Brian. Now also creating two renderbuffers, so apps can now switch with glDrawBuffer.
2006-03-30Fix logic error in viewport function so that we still resize the buffers if ↵Karl Schultz
the viewport and the window both change to the same new size. This lets the gloss demo work with the -f option.
2006-03-30When creating front/back renderbuffers, init the Red/Green/Blue/AlphaBits fieldsBrian Paul
2006-03-30Use [][3] for write_rgb_span_16Karl Schultz
2006-03-30Fixes from Brian to help migrate to render buffer DD interfaces. Also fix ↵Karl Schultz
bug in the viewport function that was using the viewport size to resize the buffer, when it should have been using the window size. Fix bug in write_rgb_span_32 where the incoming pixel data parameter was coded as a [][4] instead of [][3]. Now all the demos work correctly except singlebuffer.
2005-12-16fix thinko in last revision.Karl Schultz
2005-12-15Work In Progress. Move some of the frame buffer, render buffer, etc init ↵Karl Schultz
code from the create context path to the make current path, where it is lazily initialized. This didn't buy me very much except to make it look closer to the X11 driver. Fix up some of this same code to correct some errors. The next step is to reorganize the wmesa context data structure to inherit the gl_context by containment so I can have access to the wmesa context in the update state path. The driver is still currently not responding to changes in the Draw and Read Buffer state.
2005-09-05Add support for memory contexts (Thomas Kaltofen). Cleanup compilation ↵Karl Schultz
warnings.
2005-08-09free context structure (bug 1252316) and s/free/_mesa_free/Brian Paul
2005-05-24Major code cleanup and begin using new render buffer interface.Karl Schultz
2004-11-27Remove _mesa_ResizeBuffersMESA() call from _mesa_set_viewport().Brian Paul
Now, the driver's Viewport routine should call _mesa_ResizeBuffersMESA() if necessary. Cleaned up code related to GLframebuffer width/height initialization. Set initial viewport/scissor params in _mesa_make_current2(), instead of in the drivers' MakeCurrent functions.
2004-11-08Remove need for defining _MSC_VER when building Mesa for windows withBrian Paul
a non MS C compiler (MinGW). (Gregor Anich)
2004-10-12SWTC trick, enabled new extensionsDaniel Borca
2004-09-17rearrange a couple of lines of code to avoid compilation error in VC 6,Karl Schultz
probably due to a compiler bug.
2004-08-25Silence gcc 3.4 warnings on ReactOS. Mostly unused var warnings. (patch ↵Brian Paul
1015696)
2004-07-01Rename the various function types in t_context.h to include a tnl_ prefix.Keith Whitwell
2004-01-20Before calling _mesa_create_context(), initialize a dd_function_table structBrian Paul
by calling _mesa_init_driver_functions() and then plugging in the driver- specific functions. In particular, make sure ctx->Driver.NewTextureObject points to the appropriate driver function so that _all_ texture objects are augmented with the driver-specific data. Put in a bunch of assertions in the texture-related driver functions that texObj->DriverData is valid. Remove old dead code in near future.
2003-11-24Import vtx-0-2-branchKeith Whitwell
2003-11-04fix AccessViolation bug (#835861)Brian Paul
2003-07-24Source code for GDI driver.Karl Schultz