On Fri, Mar 1, 2013 at 6:49 AM, Pekka Paalanen wrote:
> On Fri, 1 Mar 2013 12:02:38 +0800
> Sam Spilsbury wrote:
>
>> Hi,
>>
>> I'm a little confused on the behaviour of eglSwapBuffers operating on
>> the event queue. At the moment, it calls wl_connection_read () on the
>> display fd, which will
On Fri, 1 Mar 2013 12:02:38 +0800
Sam Spilsbury wrote:
> Hi,
>
> I'm a little confused on the behaviour of eglSwapBuffers operating on
> the event queue. At the moment, it calls wl_connection_read () on the
> display fd, which will read events into the local event buffer. I
> imagine it needs to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
On 01.03.2013 06:08, Sam Spilsbury wrote:
[...]
>>> 3. For roundtrip and SwapBuffers, we could make the server put some
>>> data back into the fd indicating that the fd has been read and events
>>> were put into the queue. That way, when main
Hey, thanks for the followup
On Fri, Mar 1, 2013 at 12:50 PM, Daniel Stone wrote:
> Hi,
>
>>
>> I wanted to know what the expected behaviour around this was meant to
>> be. If eglSwapBuffers is meant to read () the fd, then that means that
>> we need to rely on it being called in order to popula
Hi,
On 28 February 2013 20:02, Sam Spilsbury wrote:
> Because all of the data has been read from the fd, there is a
> condition where we have read every single event that needed to be
> delivered to us. Then when we return to poll (), it will block
> indefinitely because there is nothing left in
Hi,
I'm a little confused on the behaviour of eglSwapBuffers operating on
the event queue. At the moment, it calls wl_connection_read () on the
display fd, which will read events into the local event buffer. I
imagine it needs to do this in order to fetch some information about
the next backbuffer
