Age | Commit message (Collapse) | Author | Files | Lines |
|
These need to be symmetric because sometimes different things need to happen in
either situation when entering the context as well.
|
|
|
|
|
|
There are two possible approaches to take here: try to expand dimensions that
are not being explicitly resized (for example expand the bottom when dragging
right), or just stop single-dimension resizes if they would go out of range.
I chose the latter here for two reasons: it's hard to always do something
smooth and unsurprising with the first approach (and it would require more
code), and it can be nice from the user's perspective to easily be able to
resize the window to exactly one of its aspect ratio limits. For example, it
is very easy to drag pugl_test to 1:1 or 16:9.
In other words, simplicity and user power wins.
|
|
|
|
I have no idea why this affects anything, but it seems to fix this, this time,
again. One of these days I'll get it right.
|
|
|
|
|
|
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.
|
|
This matches Gtk and is generally less annoying to work with.
|
|
This makes events POD, which is generally nice. The view was originally added
to reflect the display and window references in XEvent, but doesn't seem very
useful in Pugl applications.
|
|
|
|
|
|
|
|
|
|
|
|
This is a bit sloppy, but matches the typical behaviour on other platforms.
|
|
|
|
|
|
Unlike on other platforms, PeekMessage can return messages for windows other
than the given parameter (namely children). Unfortunately it doesn't seem
possible to implement this function on Windows to work exactly like on the
other platforms, but using DispatchMessage will at least dispatch them
accordingly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This avoids C++ binary compatibility and dependency hassles when
cross-compiling.
|