On 06.02.2018 13:32, finnbry...@gmail.com wrote:
> This is a clearly solvable problem (browsers do it internally)
but isn't necessarily simple, some obvious solutions:
- a way to get the texture directly on the gpu, to avoid copying back to the cpu
(likely platform and api specific, if the embed
It's been a month with the failing status check, and it's consistently a
source of confusion for developers who aren't already in the know. How
much longer are we expected to be in this state, or could we turn it off
again until it's being actively worked on?
Cheers,
Josh
On 1/4/18 5:49 PM, E
As an user of embedded browsers, I'll just chime in that whilst I agree that
99% of the api is relatively low traffic and can be cross-process with little
effort, there is 1 exception.
When embedding a common use case is that the embedder controls the final
composite into some other application
3 matches
Mail list logo
