aboutsummaryrefslogtreecommitdiffstats
path: root/pugl/detail/win_cairo.c
AgeCommit message (Collapse)AuthorFilesLines
2020-03-15Remove backend resize methodDavid Robillard1-1/+0
2020-03-15Windows: Use ephemeral Cairo surface for drawingDavid Robillard1-38/+37
2020-03-01Cleanup: Use a consistent style for all backend definitionsDavid Robillard1-9/+7
2020-02-18Pass expose event to backend enter and leave functionsDavid Robillard1-19/+17
This is needed for clipping. Unfortunately, the puglEnterContext() and puglLeaveContext() API was not suitable for this, but this shouldn't matter in user code because it is only used for setup, and is slated for removal anyway. Instead, just call the backend functions directly in the implementation.
2019-11-21Rename "backend" headersDavid Robillard1-1/+1
Working on Vulkan clarified what has always been slightly smelly about the design and organization here: not everything that is API specific is really in a "backend" (a PuglBackend). The concrete example is puglGetProcAddress(), which only makes sense for GL and is actually implemented in the "backend" files. Arguably puglGetContext() is also such a thing. So, rename the headers so they can be the place where API-specific things go in general, which happens to include a backend most of the time. The stub is a bit of an exception to this, but whatever. The includes look tidier this way. In place of the old headers are compatibility stubs that just emit a warning and include the new version, which will be maintained for a while.
2019-11-03Move platform stub configuration code to platform headersDavid Robillard1-19/+5
This allows backends which use basic software rendering (like Cairo) to share the common basic window format setup code.
2019-09-14Windows: Fix Cairo backend buildDavid Robillard1-18/+18
2019-09-07Clean up error handlingDavid Robillard1-2/+2
2019-09-03Add functions to get and set view size and positionDavid Robillard1-7/+6
2019-07-31Cleanup: Remove debug print that snuck in there somehowDavid Robillard1-1/+0
2019-07-29Reorganize source to separate private implementation detailsDavid Robillard1-0/+200
Taking a page from C++ convention, where "detail" is for things that should not be included in user code.