On Sat, Aug 3, 2013 at 12:50 AM, Carsten Haitzler ras...@rasterman.com wrote:
On Fri, 02 Aug 2013 13:52:46 -0700 Rafael Antognolli - Enlightenment Git
no-re...@enlightenment.org said:
let me get this right. if we have rendered and sent a frame off to the
compositor, we will drop/skip all
On Tue, 6 Aug 2013 11:47:37 -0300 Rafael Antognolli antogno...@gmail.com said:
On Sat, Aug 3, 2013 at 12:50 AM, Carsten Haitzler ras...@rasterman.com
wrote:
On Fri, 02 Aug 2013 13:52:46 -0700 Rafael Antognolli - Enlightenment Git
no-re...@enlightenment.org said:
let me get this right.
Is it OK if we leave it as it's now for 1.7 branch? I added this
mostly to fix the current issues caused by blocking the mainloop. I
think there are some race conditions triggered by not waiting for the
frame callback, that are making the wayland event queue to starve
waiting for events when we
On Tue, 6 Aug 2013 22:31:54 -0300 Rafael Antognolli antogno...@gmail.com said:
Is it OK if we leave it as it's now for 1.7 branch? I added this
mostly to fix the current issues caused by blocking the mainloop. I
think there are some race conditions triggered by not waiting for the
frame
On Fri, 02 Aug 2013 13:52:46 -0700 Rafael Antognolli - Enlightenment Git
no-re...@enlightenment.org said:
let me get this right. if we have rendered and sent a frame off to the
compositor, we will drop/skip all renders UNTIL the compositor sends back a
i'm done - frame presented now. right?
