Jon,
Thanks for pointing this out. I apparently missed at least one case.
I'll fix ASAP.
/Thomas
On 06/29/2011 02:20 PM, Jon TURNEY wrote:
On 28/06/2011 13:19, Thomas Hellstrom wrote:
The api and the state tracker manager code as well as the state tracker code
assumed that only a single
Looks good to me Thomas.
Jose
- Original Message -
The api and the state tracker manager code as well as the state
tracker code
assumed that only a single context could be bound to a drawable. That
is not
a valid assumption, since multiple contexts can bind to the same
drawable.
On 06/28/2011 04:27 PM, Jose Fonseca wrote:
Looks good to me Thomas.
Jose
Jakob pointed out that the state trackers (vega mesa) will actually
create a window system draw buffer / framebuffer per context, even if
they represent the same window system drawable, so I need to do some
On Tue, Jun 28, 2011 at 9:19 PM, Thomas Hellstrom thellst...@vmware.com wrote:
The api and the state tracker manager code as well as the state tracker code
assumed that only a single context could be bound to a drawable. That is not
a valid assumption, since multiple contexts can bind to the
