On 08/04/2017 04:47 AM, Michel Dänzer wrote:
On 03/08/17 11:25 PM, Thomas Hellstrom wrote:
Hi, Michel.
Thanks for doing this.
No worries, thank you for coming up with the fix in the first place. :)
Was there a follow-up st/mesa fix to this. I remember someone posting
about a problem about
On 03/08/17 11:25 PM, Thomas Hellstrom wrote:
> Hi, Michel.
>
> Thanks for doing this.
No worries, thank you for coming up with the fix in the first place. :)
> Was there a follow-up st/mesa fix to this. I remember someone posting
> about a problem about the new backbuffer always being NULL?
Hi, Michel.
Thanks for doing this. Was there a follow-up st/mesa fix to this. I
remember someone posting about a problem about the new backbuffer always
being NULL?
/Thomas
On 07/07/2017 05:29 AM, Michel Dänzer wrote:
From: Thomas Hellstrom
If the application
On 07/07/17 12:29 PM, Michel Dänzer wrote:
> From: Thomas Hellstrom
>
> If the application hasn't done any drawing since the last call, we
> would reuse the same back buffer which was used for the previous swap,
> which may not have completed yet. This could result in
From: Thomas Hellstrom
If the application hasn't done any drawing since the last call, we
would reuse the same back buffer which was used for the previous swap,
which may not have completed yet. This could result in various issues
such as tearing or application hangs.
In