aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2020-03-17Use a more logical order for PuglEventTypeDavid Robillard1-5/+5
2020-03-17Use clearer names for pointer eventsDavid Robillard8-37/+46
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.
2020-03-16Cleanup: Add missing includesDavid Robillard2-0/+4
2020-03-16Italicise the brief description of structs as with functionsDavid Robillard1-1/+1
2020-03-16Embed Demo: Add timer to occasionally reverse spin directionDavid Robillard1-2/+10
2020-03-16Simplify puglRequestAttention()David Robillard3-37/+7
Now that timers are exposed, applications can repeatedly nag for attention themselves if they really want to.
2020-03-16Add timer eventsDavid Robillard9-4/+449
2020-03-16Cleanup: Remove unused includeDavid Robillard2-1/+1
2020-03-16MacOS: Fix semantics of puglUpdate() with negative timeoutDavid Robillard1-0/+6
2020-03-16MacOS: Move initial configure to just before mapDavid Robillard1-11/+10
2020-03-16X11: Dispatch a configure event before the map for child windowsDavid Robillard1-0/+9
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.
2020-03-16Make update test more tolerantDavid Robillard1-1/+1
2020-03-16Separate cached configuration from frameDavid Robillard2-6/+3
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.
2020-03-16Factor out dispatching configure events in the drawing contextDavid Robillard4-9/+25
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.
2020-03-16Window Demo: Only redisplay on update when running continuouslyDavid Robillard1-1/+3
2020-03-16Only send update events when the view is visibleDavid Robillard3-3/+11
2020-03-15Cleanup: Fix stale commentDavid Robillard1-2/+2
2020-03-15Cleanup: Fix documentation linksDavid Robillard1-2/+2
2020-03-15Update event loop documentationDavid Robillard1-4/+14
2020-03-15Unify event loop functions as puglUpdate()David Robillard17-118/+321
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).
2020-03-15X11: Factor out flushing pending exposuresDavid Robillard1-16/+22
2020-03-15Add type and flags to worldDavid Robillard13-15/+49
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.
2020-03-15Cleanup: Add puglDispatchSimpleEvent() internal utilityDavid Robillard5-14/+21
2020-03-15Cleanup: Fix indentationDavid Robillard1-3/+3
2020-03-15Cleanup: Fix misleading variable nameDavid Robillard1-2/+2
2020-03-15Cleanup: Remove redundant PUGL_API declarationsDavid Robillard3-3/+3
2020-03-15X11: Simplify implementation slightlyDavid Robillard1-6/+2
These continue statements are not necessary since the events will not be translated anyway.
2020-03-15X11: Read from server if necessary in puglDispatchEvents()David Robillard1-3/+3
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.
2020-03-15X11: Don't use CAIRO_OPERATOR_SOURCE for blittingDavid Robillard1-1/+0
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.
2020-03-15X11: Only enter drawing context if an expose is pendingDavid Robillard1-2/+2
2020-03-15X11: Update frame immediately on ConfigureNotifyDavid Robillard1-0/+4
This fixes some jittery display issues since the frame can be used before the deferred configure actually gets dispatched.
2020-03-15X11: Factor out selection event handlingDavid Robillard1-40/+69
2020-03-15Move configure shortcut and frame update to common implementationDavid Robillard3-36/+23
2020-03-15Remove backend resize methodDavid Robillard12-43/+6
2020-03-15Windows: Use ephemeral Cairo surface for drawingDavid Robillard1-38/+37
2020-03-15Mac: Remove unnecessary resize handler in GL backendDavid Robillard1-12/+2
2020-03-15Print events in Cairo demoDavid Robillard1-0/+2
2020-03-15Remove static data from Cairo demoDavid Robillard1-44/+56
2020-03-14Add note about building local documentation to READMEDavid Robillard1-1/+3
2020-03-14Add documentation about test programsDavid Robillard1-0/+31
2020-03-14Don't generate unused config headerDavid Robillard1-1/+0
2020-03-14Add logging APIDavid Robillard8-24/+105
2020-03-13Strengthen warningsDavid Robillard6-20/+17
2020-03-09Deprecate puglEnterContext() and puglLeaveContext()David Robillard2-29/+37
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.
2020-03-09GL3 Demo: Set up and tear down GL on PUGL_CREATE and PUGL_DESTROYDavid Robillard1-19/+17
This eliminates the use of puglEnterContext().
2020-03-09GL3 Demo: Factor out GL setup and teardownDavid Robillard1-69/+102
2020-03-09Window Demo: Fix updating when not runnning continuouslyDavid Robillard2-7/+17
2020-03-09Add test for redisplays posted in the event loopDavid Robillard2-1/+134
2020-03-09Add PuglEventClient and puglSendEvent()David Robillard6-6/+128
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.
2020-03-09X11: Factor out converting PuglEventExpose to XExposeEventDavid Robillard1-16/+50
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-19 03:13:43 +0000