<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - Using old viewport value after a window resize (content is clipped)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68296#c12">Comment # 12</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED WORKSFORME - Using old viewport value after a window resize (content is clipped)"
href="https://bugs.freedesktop.org/show_bug.cgi?id=68296">bug 68296</a>
from <span class="vcard"><a class="email" href="mailto:ullysses.a.eoff@intel.com" title="U. Artie Eoff <ullysses.a.eoff@intel.com>"> <span class="fn">U. Artie Eoff</span></a>
</span></b>
<pre>Created <span class=""><a href="attachment.cgi?id=103044" name="attach_103044" title="clear color does not fill new viewport size">attachment 103044</a> <a href="attachment.cgi?id=103044&action=edit" title="clear color does not fill new viewport size">[details]</a></span>
clear color does not fill new viewport size
The problem is that the GL color buffer does not fill the GL viewport after
it's been resized. That is, after calling glViewport(...) the background color
goes black, and in the more extreme case the original clear color remains in
the portion of the previous viewport size giving the illusion of being clipped
(as seen in my attached image).
If you modify the glClearColor(...) in the sample test code to be something
other than black, then the problem becomes obvious. If then you add a
glClear(GL_COLOR_BUFFER_BIT) after the call to glViewport(...), then the
problem goes away.
The question is, is it the responsibility of the GL client program to make a
call to glClear after executing glViewport, or is Mesa supposed to handle this
for you?
The EFL developers indicate that this is only a problem on Intel platforms.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>