Download lib/python3.9/site-packages/OpenGL/GL/GREMEDY/string_marker.py from camenduru/slahmr-test: direct link, hf CLI and curl.
- Browser
- Download file 2.35 kB
-
https://huggingface.co/camenduru/slahmr-test/resolve/main/lib/python3.9/site-packages/OpenGL/GL/GREMEDY/string_marker.py
- Command line
-
hf download hf://camenduru/slahmr-test/lib/python3.9/site-packages/OpenGL/GL/GREMEDY/string_marker.py
-
curl -L -o string_marker.py https://huggingface.co/camenduru/slahmr-test/resolve/main/lib/python3.9/site-packages/OpenGL/GL/GREMEDY/string_marker.py
2.35 kB
| '''OpenGL extension GREMEDY.string_marker | |
| This module customises the behaviour of the | |
| OpenGL.raw.GL.GREMEDY.string_marker to provide a more | |
| Python-friendly API | |
| Overview (from the spec) | |
| This extension defines a mechanism to insert textual markers into | |
| the OpenGL stream. | |
| When debugging or profiling an OpenGL application some of the most | |
| important tools are stream loggers, which just output a list of the | |
| called OpenGL commands, and profilers, which show at which points | |
| the pipeline is bottlenecked for a given part of the frame. The | |
| problem in using these is that there is a definite loss of | |
| information between the application and the used debugger/profiler. | |
| The application generally has a pretty good idea what is rendered | |
| when (e.g. rendering background, landscape, building, players, | |
| particle effects, bullets etc.), but the debugger/profiler only | |
| sees the OpenGL stream. To analyze the stream developers have to | |
| guess what is done when by following the program code and the log | |
| output in parallel, which can get difficult for systems that | |
| restructure their internal pipeline or do lazy changes. | |
| This extension is really only useful for these debuggers and | |
| profilers, and not for actual drivers. In fact, it is not expected | |
| that any standard driver would ever implement this extension. The | |
| main point of having this extension is to allow applications to have a | |
| clean way of accessing this functionality only when they are run | |
| under the control of a debugger/profiler, without having to | |
| recompile or change the application source code. | |
| The official definition of this extension is available here: | |
| http://www.opengl.org/registry/specs/GREMEDY/string_marker.txt | |
| ''' | |
| from OpenGL import platform, constant, arrays | |
| from OpenGL import extensions, wrapper | |
| import ctypes | |
| from OpenGL.raw.GL import _types, _glgets | |
| from OpenGL.raw.GL.GREMEDY.string_marker import * | |
| from OpenGL.raw.GL.GREMEDY.string_marker import _EXTENSION_NAME | |
| def glInitStringMarkerGREMEDY(): | |
| '''Return boolean indicating whether this extension is available''' | |
| from OpenGL import extensions | |
| return extensions.hasGLExtension( _EXTENSION_NAME ) | |
| # INPUT glStringMarkerGREMEDY.string size not checked against len | |
| glStringMarkerGREMEDY=wrapper.wrapper(glStringMarkerGREMEDY).setInputArraySize( | |
| 'string', None | |
| ) | |
| ### END AUTOGENERATED SECTION |