Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Process events in runloop only when needed #4399

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

Jacalz
Copy link
Member

@Jacalz Jacalz commented Nov 18, 2023

Description:

This PR changes the run loop to use glfw.WaitEvents() instead and use glfw.PostEmptyEvent() when necessary to only ever process events when there are any to process.

This specific PR is a rebase of #4173. It was easier to start fresh.

Fixes #2506

Checklist:

  • Tests included.
  • Lint and formatter run with no errors.
  • Tests all pass.


postEmptyEvent()

eventTick := time.NewTicker(time.Second / 60) // TODO: Why does it not work without this?
Copy link
Member Author

@Jacalz Jacalz Nov 18, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I get no window without this ticker and I just don't understand why. If the glfw.WaitEvents() method blocks as it's supposed to, surely this loop won't run more times because we have a ticker (that in theory ought to make sure run less compared to a bare for {})?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you saying it works with the ticker but not the bare for{}?
If so my guess would be that its blocking the posting of other events that you're expecting will wake it up.
You could test by switching to [glfwWaitEventsTimeout](https://www.glfw.org/docs/3.3/group__window.html#ga605a178db92f1a7f1a925563ef3ea2cf)(0.7); and see if it helps

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you saying it works with the ticker but not the bare for{}?

Yup. I am worried that glfwWaitEventsTImout will be just as bad as the previous code unless we have a very long timeout.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It was not meant as a solution, merely more data for debugging

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think postEmtpyEvent at line 120 needs to be in a goroutine so that we have called waitEvents before postEmptyEvent is called. Doing that seems to launch the window in my testing without using the ticker.

The real challenge is figuring out everywhere we would now need to PostEmtpyEvent to wake up the main thread. Especially on ARM Mac where we draw on the main thread it will be a challenge, since the waitEvents call will need to be woken up whenever there's something that needs to be drawn/refreshed.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, cool. I'll keep that in mind and look at this once again going forward

Copy link
Member

@andydotxyz andydotxyz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

a good work to move to a more efficient approach.
Offering some suggestions inline.


postEmptyEvent()

eventTick := time.NewTicker(time.Second / 60) // TODO: Why does it not work without this?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are you saying it works with the ticker but not the bare for{}?
If so my guess would be that its blocking the posting of other events that you're expecting will wake it up.
You could test by switching to [glfwWaitEventsTimeout](https://www.glfw.org/docs/3.3/group__window.html#ga605a178db92f1a7f1a925563ef3ea2cf)(0.7); and see if it helps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants