On 02/06/2015 11:58 PM, Chad Versace wrote:
On 02/05/2015 04:45 AM, Tapani wrote:
On 02/05/2015 09:47 AM, Tapani Pälli wrote:
On 02/03/2015 10:07 PM, Chad Versace wrote:
It seems that two solutions are available:
S1. Provide waffle_set_swap_buffers_callback().
S2. On Waffle's NaCl
On 02/05/2015 09:47 AM, Tapani Pälli wrote:
On 02/03/2015 10:07 PM, Chad Versace wrote:
It seems that two solutions are available:
S1. Provide waffle_set_swap_buffers_callback().
S2. On Waffle's NaCl backend, implement waffle_swap_buffers() to
block
until the back buffer has
On 02/03/2015 10:07 PM, Chad Versace wrote:
On 01/30/2015 02:33 AM, Tapani Pälli wrote:
Hi;
As a Finn I interpret silence as 'yes' :)
A safe assumption in many open source cultures :)
So I started to hack on swap completion event support. I believe it
can be useful for other backends
On 01/30/2015 02:33 AM, Tapani Pälli wrote:
Hi;
As a Finn I interpret silence as 'yes' :)
A safe assumption in many open source cultures :)
So I started to hack on swap completion event support. I believe it
can be useful for other backends also since then application can
throttle
Hi;
As a Finn I interpret silence as 'yes' :) So I started to hack on swap
completion event support. I believe it can be useful for other backends
also since then application can throttle rendering and receive
information on swaps.
I made early hacky prototype that fixes the issues I've
Hello;
Unfortunately I've noticed a problem with the implementation. Native
client expects 3D API to be used so that caller passes a callback that
gets called when swapbuffers finishes. I haven't found explicit
documentation of this to be *mandatory* but all the examples work this
way and
6 matches
Mail list logo
