Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
|
|
|
|
This makes it unlikely for tests to be completely obscured, which should
hopefully make things a bit more consistent and reliable, especially when
running all of the tests in parallel. It also makes things a bit less visually
confusing.
|
|
This seems to make thing a bit more reliable, and matches what was happening
before the addition of more precise show commands.
|
|
|
|
|
|
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.
|
|
|
|
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.
|
|
This collapses many functions into one, which makes the API more easily
extensible and reduces code size.
|
|
|
|
See https://reuse.software/ for details.
|
|
This makes things a little more clear when something goes wrong, for example if
a test hangs.
|
|
|