Skip to content
This repository has been archived by the owner on Jul 15, 2024. It is now read-only.

Re-introduce paint in Windows backend #9

Open
bzm3r opened this issue Oct 14, 2022 · 1 comment
Open

Re-introduce paint in Windows backend #9

bzm3r opened this issue Oct 14, 2022 · 1 comment
Labels
unpiet Uncoupling piet and glazier

Comments

@bzm3r
Copy link
Contributor

bzm3r commented Oct 14, 2022

Commented out by unpiet process.

See:

// pub mod dcomp;

and:

//pub mod paint;

@bzm3r bzm3r added the unpiet Uncoupling piet and glazier label Oct 14, 2022
@bzm3r bzm3r changed the title Re-introduce dcomp and paint in Windows backend Re-introduce dcomp and paint in Windows backend? Oct 14, 2022
@raphlinus
Copy link
Contributor

raphlinus commented Oct 14, 2022

I suspect that dcomp should probably not be done here, as I don't believe raw_window_handle can eventually plumb down to CreateSwapchainForComposition; I believe it only the CreateSwapChainForHwnd method can be wired up. That said, I think plumbing WM_PAINT to paint() probably does seem like a good idea, as a way to trigger repaint cycles that end up in a Present call.

Composition is way out of scope for now, but might be on the long term roadmap. See raphlinus/raphlinus.github.io#77 for more thoughts on that.

@bzm3r bzm3r changed the title Re-introduce dcomp and paint in Windows backend? Re-introduce paint in Windows backend Oct 14, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
unpiet Uncoupling piet and glazier
Projects
None yet
Development

No branches or pull requests

2 participants