Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
Towards a more direct and explicit mapping to platform hints, and more
consistent behaviour across platforms. OpenGL applications are generally
expected to be explicit about hints like this.
|
|
|
|
|
|
|
|
Since this is essentially a destructor, I don't think there's anything really
useful to do with errors here, and in practice no backends actually used it
anyway.
|
|
|
|
See https://reuse.software/ for details.
|
|
This fixes getting the PUGL_SWAP_INTERVAL hint on some NVidia drivers.
|
|
|
|
GLX_CONTEXT_COMPATIBILITY_PROFILE_BIT_ARB is the correct counterpart to
GLX_CONTEXT_CORE_PROFILE_BIT_ARB in this context. This has the same value as
the GLX_CONTEXT_FORWARD_COMPATIBLE_BIT_ARB it replaces though, so this change
should not actually affect anything.
|
|
Aside from reading more naturally, this avoids clashes with types that are not
events, like PuglEventFlags. This is also more consistent with the C++
bindings, where "EventExpose" would be quite strange, for example.
Apologies for the noise. Aliases to the old names will be preserved in the
deprecated API like other things for a short while.
|
|
|
|
|
|
These will not be used in the Sphinx documentation, and most were
self-explanatory and only there to make the Doxygen index look nice anyway.
Where there was actually useful information, it has been preserved as regular
comments.
|
|
These only do anything for OpenGL, and it seems unlikely that they will ever be
used for anything else. So, move them to the GL headers to remove clutter from
the core API, and ensure that they are only used in GL applications that
include the appropriate headers and link with a GL backend.
Also add missing C++ bindings.
|
|
This was missing from the C++ bindings and barely used anyway, so just remove
it for now in the interests of simplicity and finalizing a stable API.
The information previously logged in the X11 GL backend is now available
programatically, so applications can print the same information portably if
they like.
|
|
|
|
I think this attempt to be optionally header-only was misguided, particularly
installing source code to the system include path. Typically anyone vendoring
code just includes the repository and builds from there anyway.
This commit moves all the implementation code to a typical src directory (Don't
Be Weird).
I still think there is some value in simple "inline" deployment, but that would
be better achieved another way, like producing a single-file amalgamation that
builds anywhere, ala sqlite.
|