Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
|
|
|
|
Towards fully separating position from size.
|
|
|
|
|
|
|
|
As far as I can tell, nobody actually cares about this in practice now, and
it's slated for removal anyway.
|
|
Appeases the cert-int09-c and readability-enum-initial-value checks added in
clang-tidy 19.
|
|
|
|
|
|
For consistency with event types (since "obscure" is opposite "expose") and the
upcoming puglObscureRegion().
|
|
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).
|
|
|
|
These could be combined into a hint-like general get/set mechanism, but
currently there's only two window relationships and no immediate plans to add
more, so that feels a bit over-engineered. So, just rename for consistency
with puglSetTransientParent().
|
|
This isn't a strict enumeration anyway, so a sentinel value does no harm, and
using it avoids warnings about testing an enum with no zero value.
|
|
|
|
|
|
|
|
This reduces diff noise and merge conflicts, and at least basic C99 support is
deeply required anyway.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The GLU library is often shipped in a separate package, so it's possible to
have a system with GL, but no GLU headers. Since use of GLU isn't
universal (none of the examples use it), its inclusion can break builds that
would otherwise work. So, move it to a separate wrapper header so this can be
avoided.
|
|
|
|
|
|
I don't know if vendoring the Vulkan library is appropriate, but regardless,
this allows applications to set the name to whatever they want, or specify an
absolute path, just in case the standard value baked into Pugl isn't the right
one in some situation.
|
|
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.
|
|
This replaces the window title and class name APIs with a more general one that
can be easily extended to other things, like icon names, more detailed
application hints, and so on.
|
|
|
|
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
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.
|
|
|
|
This becomes important when the documentation is included in larger projects.
|
|
|
|
|
|
|
|
|
|
These inform the compiler that the returned value doesn't alias with anything.
Also somewhat handy as pseudo-documentation.
|
|
|
|
On MacOS in particular, views and windows are entirely different concepts, so
confusing them... confuses things. This was the last holdover in the API that
used the old "native window".
|