You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 15, 2024. It is now read-only.
Which leads me to wonder: does the presentation strategy logic also not belong in glazier? That seems to clash with my understanding of the purpose of glazier, so I'm wondering if I can have some insight.
The text was updated successfully, but these errors were encountered:
The presentation logic probably doesn't belong in glazier now, but it should likely be revisited when we tackle how to integrate frame pacing (and window resize, which really isn't a problem any Windows GPU integration designed in the last 5 years even attempts to tackle).
I am working on silencing some clippy lints, which is pointing me to consider what is happening with regards to presentation strategy in druid-shell:
glazier/src/backend/windows/window.rs
Line 741 in 15306d1
compared to in
unpiet
, where presentation strategy logic goes out the window:glazier/src/backend/windows/window.rs
Line 689 in 03691e7
Tracing various threads back, I am lead to the blocker being
create_dxgi_state
, particularly the creation of aD3D11Device
, as explained by Raph here.Which leads me to wonder: does the presentation strategy logic also not belong in
glazier
? That seems to clash with my understanding of the purpose of glazier, so I'm wondering if I can have some insight.The text was updated successfully, but these errors were encountered: