That's very inefficient, on top of questionable tech stack
Why would you store the screenshot to disk, just grab what ever the compositor gives you and render it on a texture, skipping the whole disk write usage
I thought it will be fun to do this with this tech stack, and I didn't want to spend an entire week for a magnifier. It's also cool to see what you can build with a web stack!
I'm not sure why this would be so inefficient, as the screenshot is only taken once when the magnifier is activated. In fact, I don't think we care about efficiency at all for this kind of little tool.
But thanks a lot for the link, that's super interesting, and they included a "ExcludeFromCapture" which would have been very convenient! I'll have a look how if I can integrate this into a Tauri backend!
I'm not sure why this would be so inefficient, as the screenshot is only taken once when the magnifier is activated. In fact, I don't think we care about efficiency at all for this kind of little tool.
But thanks a lot for the link, that's super interesting, and they included a "ExcludeFromCapture" which would have been very convenient! I'll have a look how if I can integrate this into a Tauri backend!