aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2025-03-05X11: fix BadWindow for embedded windows when the parent is destroyedHEADmainQuant1um1-0/+3
2025-03-05Disable meson implicit include directories anti-featureDavid Robillard16-0/+28
2025-02-11Sort meson optionsDavid Robillard1-6/+6
2025-02-09Windows: Avoid over-linking system librariesDavid Robillard1-1/+3
2025-02-09Avoid including gl.h in pugl_shader_demoDavid Robillard1-0/+2
This conflicts with GLAD.
2025-02-09Adhere to minimum image count in pugl_vulkan_cpp_demoDavid Robillard1-1/+1
2025-02-09Make pugl_vulkan_cpp_demo explicitly opaqueDavid Robillard1-1/+1
2025-02-09Use angle brackets for puglutil includesDavid Robillard27-35/+31
The convention here is that quotes are used for paths relative to the current file only.
2025-02-08Fix puglIsvalidPosition()David Robillard1-1/+2
Most obivously, this made top-level views initially invisible on Windows because they were placed at (-32768, -32768).
2025-02-08Remove PuglRect entirelyDavid Robillard2-20/+0
This is no longer used internally, and overall, I've found it to be more of a hassle than a convenience in client code. It's also arguably questionable to have a "flat" rectangle when point and area types exist (compare with NSRect, for example). Also towards fully separating position from size and discouraging the joining of them in general, towards Wayland and to discourage common plugin GUI bugs.
2025-02-08Avoid PuglRect in size testDavid Robillard1-10/+12
2025-02-08Replace frame with size and position hintsDavid Robillard32-226/+315
2025-02-08Add PUGL_CURRENT_SIZE hint and make size hints dynamicDavid Robillard5-34/+55
2025-02-08Remove puglSetFrame()David Robillard6-124/+7
Towards fully separating position from size.
2025-02-08MacOS: Avoid puglSetFrame() in puglRealize()David Robillard1-7/+15
2025-02-08MacOS: Avoid puglSetFrame() in puglSetPosition() and puglSetSize()David Robillard1-20/+19
2025-02-08Simplify and shorten enumerator commentsDavid Robillard1-3/+3
2025-02-08Add missing C++ binding definitionsDavid Robillard1-0/+8
2025-02-07Fix accidentally exported symbolDavid Robillard1-1/+0
2025-02-07Update clang-format configurationDavid Robillard15-186/+103
2025-02-07Use angle brackets for library includes and clean up include pathsDavid Robillard87-187/+156
2025-02-07Move test utilities to a separate subprojectDavid Robillard42-52/+74
Towards sorting out sloppy include directories, and avoiding upward-relative paths in includes. A subproject seems like overkill, but this is the only way I can think of that makes for a clean local dependency that doesn't rely on anything non-standard or trigger any linters.
2025-02-07Add C++ bindings to meson configuration summaryNedko Arnaudov1-0/+1
2025-02-06Add option to disable C++ bindingsDavid Robillard5-9/+29
2025-02-06Remove deprecated APIDavid Robillard12-660/+1
As far as I can tell, nobody actually cares about this in practice now, and it's slated for removal anyway.
2025-02-06Suppress new checks in clang-tidy 19David Robillard1-0/+1
I get that these aren't all intended to be universal, but suggesting the replacement of standard functions with boost ones is completely backwards. This is what a lack of a pluggable architecture gets you.
2025-02-06Fully parenthesize mathematical expressionsDavid Robillard6-21/+23
Well, on X11 where I'm running clang-tidy anyway, there may be some stragglers in the other platform implementations. Appeases the readability-math-missing-parentheses check added in clang-tidy 19.
2025-02-06Fully parenthesize mathematical expressionsDavid Robillard3-7/+8
2025-02-06Explicitly specify all PuglKey valuesDavid Robillard1-71/+71
Appeases the cert-int09-c and readability-enum-initial-value checks added in clang-tidy 19.
2025-02-06Gracefully handle failing return from ftell()David Robillard2-8/+17
Again I don't think this is actually a concern, but it appeases clang-tidy.
2025-02-06X11: Gracefully handle failure of clock_gettime()David Robillard1-1/+4
As gracefully as possible given the API anyway. I don't think this is an error case that happens enough to really need transparent error handling, if the clock doesn't work all is lost anyway. Appeases cert-err33-c, which started caring about clock_gettime() in clang-tidy 19.
2025-02-06Update whitespaceDavid Robillard1-1/+2
Apparently clang-format 19 decided to get even worse in this case. The C and C++ committes really, really should have sorted out this nonsense a decade ago.
2025-02-06Fix typoDavid Robillard1-2/+2
2025-02-01Consistently use unsigned literals for event flagsDavid Robillard5-33/+33
2025-01-31Windows: Improve clipboard reliabilityDavid Robillard1-2/+15
2025-01-31Windows: Actually use impl variablesDavid Robillard1-14/+13
2025-01-31Windows: Ignore return value of SetForegroundWindowDavid Robillard1-1/+1
It turns out that this is flaky for reasons that aren't terribly clear from the documentation. So, just ignore it, it's not the end of the world if raising doesn't happen anyway.
2025-01-31Windows: Improve error handlingDavid Robillard1-46/+30
2025-01-31Windows: Simplify message pollingDavid Robillard1-21/+6
The internal puglPollWinEvents() abstraction was doing more harm than good.
2025-01-31Windows: Avoid using a floating point loop counterDavid Robillard1-1/+3
2025-01-23Replace puglPostRedisplayRect() with puglObscureRegion()David Robillard9-66/+129
2025-01-23Rename puglPostRedisplay() to puglObscureView()David Robillard18-44/+58
For consistency with event types (since "obscure" is opposite "expose") and the upcoming puglObscureRegion().
2025-01-23Draw position, size, and scale in pugl_management_demoDavid Robillard1-3/+21
2025-01-23Update clant configurationDavid Robillard1-4/+0
2025-01-23Simplify some conditionalsDavid Robillard1-3/+4
2025-01-22Simplify initial position code and place children at the originDavid Robillard5-134/+121
The code to find the initial size and position for a view had a lot of duplication, and was inconsistent between platforms. Flaky positioning and attempting to center embedded children has historically caused a bunch of problems in general, particularly since windows can be resized. So, factor out all the initial size and position code so that the logic is in one centralized place used by all platforms, and always position embedded children within their parent at the top/left origin. For top-level windows, the view is centered on its transient parent or the screen (as before). A new platform function puglGetAncestorCenter() is used to do this in general code. Also towards a total separation of position and size, towards support for Wayland, where applications don't dictate their own positions.
2025-01-22Factor out puglIsValidSize()David Robillard5-5/+14
2025-01-22Factor out puglIsValidPosition()David Robillard6-8/+17
2025-01-22Rename PuglViewSize to PuglAreaDavid Robillard7-36/+36
2025-01-22Make puglSetSizeHint() consistent with puglSetSize()David Robillard7-37/+45
In general, it's more convenient to have full-width integers as parameters, since C will promote any arithmetic on smaller types to them anyway. Using narrow types here, then, doesn't really make anything stricter, just forces an annoying cast when lots of warnings are enabled, which is likely unchecked. Better to handle it here, since it's more convenient, and the integer range checks the compiler can do aren't correct anyway (the max width/height is intentionally smaller than the max PuglSpan, so it can fit in a signed 16-bit integer).
generated by cgit v1.2.1 (git 2.18.0) at 2025-03-31 17:45:58 +0000