Windows appear corrupt when resized beyond GL_MAX_TEXTURE_SIZE
Bug #1393630 reported by
Daniel van Vugt
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mir |
New
|
Medium
|
Unassigned | ||
| mir (Ubuntu) |
New
|
Medium
|
Unassigned | ||
Bug Description
Windows appear corrupt when resized beyond GL_MAX_
But that's OK. This is precisely what the tessellate function is for. We just need to adapt to having the client buffer divided into potentially multiple textures.
| Changed in mir: | |
| importance: | Undecided → Medium |
Revision history for this message
| Daniel van Vugt (vanvugt) wrote | #1 |
Revision history for this message
| Michał Sawicz (saviq) wrote | #2 |
| Changed in mir (Ubuntu): | |
| importance: | Undecided → Medium |
To post a comment you must log in.
In the duplicate bug kdub suggested limiting resizes to the max texture size. That would be hackish and also an artificial limitation. We can create larger buffers already without any problem. The only issue is how to render them. So I would prefer we changed the rendering method rather than preventing resize requests (which do succeed just fine).
On modern hardware this might not be a problem at all. I suspect GL_MAX_TEXTURE_SIZE is staying sufficiently ahead of common display resolutions that we won't need to fix this bug in a hurry.