Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
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.
|
|
|
|
Now that timers are exposed, applications can repeatedly nag for attention
themselves if they really want to.
|
|
|
|
|
|
|
|
|
|
It does not seem to be guaranteed that child windows receive a ConfigureNotify
at all. Work around this by explicitly dispatching one first, so child views
receive events consistently with how top level views do.
|
|
This was a bad idea and a never-ending source of problems. The frame
represents what the "current" frame is from a Pugl perspective, but with the
asynchronicity of X11 and other issues this cant be used to filter configure
events.
Instead, simply cache the last configure event that was sent and compare with
that.
|
|
The updates here need to happen whenever a configure is dispatched, even
outside puglDispatchEvent(). This removes the last remaining direct calls to
the event callback so the common implementation can always do the right thing.
|
|
|
|
|
|
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).
|
|
|
|
Unfortunately this is an API break, but there's no reasonable way to deprecate
the old function and this is required for things to work correctly. The type
will be used in following commits to tick the main loop and dispatch events
correctly for either case.
|
|
|
|
|
|
|
|
These continue statements are not necessary since the events will not be
translated anyway.
|
|
This reduces input lag. The previous approach was an over-optimization: what's
important here is to keep the iteration bounded by not continually flushing,
but we do want to read everything to be as up to date as possible.
|
|
This causes artifacts in some scenarios. Although CAIRO_OPERATOR_SOURCE should
be faster, the default operator works better in the absence of real double
buffering.
|
|
|
|
This fixes some jittery display issues since the frame can be used before the
deferred configure actually gets dispatched.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
These are prone to abuse, and have caused confusion with people who try to use
them like in other libraries that support explicit drawing in the main loop.
The drawing parameter was also wrong, and these were already just compatibility
veneers since the internal context API needs to be more expressive.
So, now that PUGL_CREATE and PUGL_DESTROY exist, they can be deprecated to
force clients to draw only at the correct time.
|
|
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.
|
|
|
|
|
|
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
|
|
|
|
|
|
Apparently glxext.h is always included in glx.h on modern systems.
The window demo does not actually use any GL functions directly since they are
all factored out.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This dispatches events on a per-window basic instead of globally, using the
same mark trick as before to bound the number of events dispatched.
After the events are dispatched, all the windows are updated if they have an
invalid region. This ensures that all windows get drawn every iteration if
necessary, since Windows itself does not send WM_PAINT messages if there is
lots of input activity.
|
|
|
|
|