Skip to content
Discussion options

You must be logged in to vote

I think this is caused by the tick handler leaving EventContext.consume_event set, which then leaks into the next queued input event. If you apply this patch to main, does that resolve the issue?

diff --git a/src/vxfw/App.zig b/src/vxfw/App.zig
index 7fec41a..1d0ae94 100644
--- a/src/vxfw/App.zig
+++ b/src/vxfw/App.zig
@@ -128,11 +128,7 @@ pub fn run(self: *App, widget: vxfw.Widget, opts: Options) anyerror!void {
             try loop.queue.lock();
             defer loop.queue.unlock();
             while (loop.queue.drain()) |event| {
-                defer {
-                    // Reset our context
-                    ctx.consume_event = false;
-                    ctx.phase = .captu…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@Lilweavs
Comment options

Answer selected by Lilweavs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants