-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Using eventsloop only as source of events #420
Copy link
Copy link
Closed
Labels
C - waiting on authorWaiting for a response or another PRWaiting for a response or another PRD - hardLikely harder than most tasks hereLikely harder than most tasks hereDS - x11Affects the X11 backend, or generally free Unix platformsAffects the X11 backend, or generally free Unix platformsF - questionThere's no such thing as a stupid oneThere's no such thing as a stupid oneP - highVital to haveVital to haveS - apiDesign and usabilityDesign and usability
Milestone
Description
Metadata
Metadata
Assignees
Labels
C - waiting on authorWaiting for a response or another PRWaiting for a response or another PRD - hardLikely harder than most tasks hereLikely harder than most tasks hereDS - x11Affects the X11 backend, or generally free Unix platformsAffects the X11 backend, or generally free Unix platformsF - questionThere's no such thing as a stupid oneThere's no such thing as a stupid oneP - highVital to haveVital to haveS - apiDesign and usabilityDesign and usability
Hey,
I want to use eventsloop only as a source of events for my actual main loop to receive. For this, I run it in another thread. Polling is not an acceptable solution.
Now I have the same problem as specified in #239: Window methods like
get_inner_size()are blocking when the eventsloop is asleep. Could you clarify if this usage is supported? If it isn't, why would Window be Send + Sync?