aboutsummaryrefslogtreecommitdiffstats
path: root/test/test_utils.h
AgeCommit message (Collapse)AuthorFilesLines
2023-05-03Fix mismatched format specifiersDavid Robillard1-1/+1
2023-01-14Windows: Add PUGL_DARK_FRAME hintDavid Robillard1-0/+2
This allows dark applications to visually integrate more nicely in Windows 10. A little thing, but it really goes a long way to make programs not look out of place and half-baked.
2023-01-08Add support for OpenGL ES 3.2 in pugl_shader_demoDavid Robillard1-1/+23
2023-01-08Prepare OpenGL context flags for OpenGL ES supportDavid Robillard1-4/+6
2023-01-08Add PUGL_SAMPLE_BUFFERS hintDavid Robillard1-0/+2
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.
2023-01-07Replace map/unmap events with more expressive configure eventsDavid Robillard1-4/+2
2023-01-07Add support for special view types and stylesDavid Robillard1-6/+43
2023-01-07Rename create/destroy events to realize/unrealizeDavid Robillard1-4/+4
As evidence that this was confusing, the documentation for these was an outright lie, and I've burned quite a bit of time in the past few days trying to rework things based around that flawed understanding. These names make it clear what these events actually are. If we need actual create/destroy events with a broader scope, they'll have to be added, but I suspect those aren't actually useful anyway.
2022-06-07Use a consistent scheme for enum sizesDavid Robillard1-3/+1
2022-05-23Add rich clipboard supportDavid Robillard1-1/+5
This implements a more powerful protocol for working with clipboards, which supports datatype negotiation, and fixes various issues by mapping more directly to how things work on X11.
2022-05-21Use consistent integer types for view positions and sizesDavid Robillard1-11/+14
Actual window sizes and positions fit easily in a 16-bit integer. So, we use that in "representation contexts" like events. This makes structures smaller, and allows the values to be converted to float, double, or integer without casting (since any int16_t or uint16_t value can fit in them without loss). Setter APIs use native integers for convenience, to avoid casting hassles when doing arithmetic. Ranges are checked at runtime.
2022-04-23Move reserved platform defines from code to build systemDavid Robillard1-2/+0
Numerous things warn about this, and it's generally a bad idea to put these in the code since it can result in incompatibly compiled code being linked together. Unfortunately this makes building manually (without the build system) more fiddly, but such is life.
2021-12-17Adopt REUSE machine-readable licensing standardDavid Robillard1-15/+2
See https://reuse.software/ for details.
2021-12-17Remove unnecessary includeDavid Robillard1-1/+0
2021-05-08Print create/destroy and map/unmap events in tests by defaultDavid Robillard1-8/+8
2021-04-18Fix unreachable codeDavid Robillard1-1/+1
2021-01-02Simplify clang-format configuration and format all codeDavid Robillard1-256/+256
2020-10-24Replace live resize with loop eventsDavid Robillard1-2/+6
This allows the application to control how recursive loops are handled rather than have Pugl impose behavior which can get in the way. For example, an application may not want to continuously animate while being resized, or set up its rendering differently in this situation. For example, with Vulkan, setting up a different swapchain can be necessary for smooth performance while live resizing on Windows, and Pugl has no ability to do this. I think it was a mistake to add this timer to Pugl itself, because it was always a bit of a leaky abstraction, and not very appropriate for a library that is supposed to be a thin abstraction layer. Though it almost seemed like things ran as usual while resizing on Windows and MacOS, the main event loop being stalled can be confusing, and there was no way to detect this. This way, applications must explicitly handle this situation and can implement the behavior they want without Pugl getting in the way. This also simplifies the Pugl implementation a bit, which is always nice.
2020-10-21Fix clang-tidy issues in Windows codeDavid Robillard1-1/+1
2020-10-21Add missing include guardsDavid Robillard1-0/+5
2020-10-04Add refresh rate hintDavid Robillard1-0/+2
2020-10-04Print all view hints in shader demo and hint testsDavid Robillard1-0/+53
2020-07-05Add scroll direction fieldDavid Robillard1-1/+21
2020-07-05Print crossing mode of enter and leave eventsDavid Robillard1-4/+6
2020-07-05Replace grab flag in PuglEventFocus with crossing modeDavid Robillard1-4/+19
2020-05-16Use email address in copyright headersDavid Robillard1-1/+1
Not really sure why I used a web link here (maybe because it's more stable), but this is more conventional.
2020-04-04Fix mismatched printf parameter warningDavid Robillard1-2/+1
Compilers are allowed to choose signed or unsigned for enums, and apparently gcc and c++ make different choices.
2020-03-31Add format attribute to logError()David Robillard1-1/+8
2020-03-31Fix mismatched printf parameter typesDavid Robillard1-2/+2
2020-03-17Use clearer names for pointer eventsDavid Robillard1-3/+3
These old "notify" names are a smell from X11 which is a bit strange and inconsistent here, since nearly everything is a "notification" of sorts. I think the new names here are much more clear since they are consistent with the keyboard focus events.
2020-03-16Add timer eventsDavid Robillard1-0/+2
2020-03-15Unify event loop functions as puglUpdate()David Robillard1-1/+3
The previous separation between polling and dispatching was a lie, especially on MacOS where it is impossible to only poll for events without dispatching anything. Providing such an API is misleading, and problematic in various other ways. So, merge them into a single puglUpdate() function which can do the right thing on all platforms. This also adds the behaviour of actually processing all events in the given time interval, which is almost always what clients actually want to do when using a positive timeout (naively doing this before caused terrible input lag).
2020-03-09Add PuglEventClient and puglSendEvent()David Robillard1-0/+8
This event makes it possible to send an arbitrary event to a view, which is useful for many things. In particular, this method of communication with views will wake up the event loop, unlike hacks in applications that share data in some other way.
2020-03-09Add create, destroy, map, and unmap eventsDavid Robillard1-0/+8
These can be used to do things when a view is created or destroyed, in particular set up the GL context in a more controlled way. Map and unmap events are also added for when views are shown and hidden so application can react to this as well. Towards the deprecation of puglEnterContext() and puglLeaveContext(), which are prone to abuse. squash! Remove client event stuff
2020-03-08Enable double buffering by defaultDavid Robillard1-3/+3
2020-03-08Add vsync command line options to demosDavid Robillard1-2/+19
2020-03-08Split graphical utilities out from test_utils.hDavid Robillard1-149/+1
2020-03-08Print when unknown events are received in testsDavid Robillard1-0/+3
2020-03-01Cleanup: Adjust some code to be more clang-format friendlyDavid Robillard1-0/+6
2020-03-01Cleanup: Shorten event printing codeDavid Robillard1-42/+63
2019-12-09Fix use of incorrect union elementDavid Robillard1-4/+4
2019-11-18Add test utility function for logging errorsDavid Robillard1-1/+15
2019-11-18Add error checking option to test programsDavid Robillard1-1/+5
2019-11-03Add verbose option to test programs to print all eventsDavid Robillard1-9/+43
2019-09-07Add OpenGL 3 test programDavid Robillard1-0/+58
2019-09-03Factor out parsing test optionsDavid Robillard1-0/+58
2019-09-03Make pugl_test use a nested view and test focus and movementDavid Robillard1-48/+43
2019-09-03Move puglGetTime() to PuglWorldDavid Robillard1-4/+4
2019-08-02Test: Factor out FPS printerDavid Robillard1-3/+26
2019-07-24Unify key and character fields and separate text eventsDavid Robillard1-9/+8
Only one field is necessary to store any kind of key, including special keys, since PuglKey occupies a reserved Unicode region. This is generally much simpler to deal with since there is only one value to dispatch on. Text events are separated from key events (like Windows but unlike MacOS or X11) because it is not possible to derive text events from key press events when they occur on Windows. Since merging the two has been the source of some confusion, this approach has some advantages anyway, even though it introduces the need to handle another event type. In the process, text input has been almost completely rewritten. I have tested this with a compose key on X11 and dead keys on Windows and MacOS and everything seems to work correctly, though there may (as always) still be issues with more exotic input methods.