<div dir="ltr">About tests: most of the ones that rely on non-antialised rendering (especially depth compositing) specifically turn it off. I suspect there won't be any regressions.<div><br></div></div><div class="gmail_extra">
<br clear="all"><div>David E DeMarle<br>Kitware, Inc.<br>R&D Engineer<br>21 Corporate Drive<br>Clifton Park, NY 12065-8662<br>Phone: 518-881-4909</div>
<br><br><div class="gmail_quote">On Tue, Aug 6, 2013 at 5:23 PM, David Gobbi <span dir="ltr"><<a href="mailto:david.gobbi@gmail.com" target="_blank">david.gobbi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Tue, Aug 6, 2013 at 2:09 PM, Sean McBride <<a href="mailto:sean@rogue-research.com">sean@rogue-research.com</a>> wrote:<br>
> On Mon, 5 Aug 2013 16:41:22 -0600, David Gobbi said:<br>
</div><div class="im">>>Sample buffers supported in OS X since 10.2. Is this safe on all OS X<br>
>>machines? Is it possible that it could cause creation of the context<br>
>>to fail if the gfx card does not support sample buffers?<br>
><br>
> As I know next to nothing about OpenGL (VTK is my abstraction :)) I can't speak to this change really... but some thoughts:<br>
><br>
> - any performance change?<br>
<br>
</div>Probably some, but none that I can perceive. Multisamples have been<br>
on by default on all other platforms (including Carbon) since at least<br>
2007. Only Cocoa was left out. It can be turned off.<br>
<div class="im"><br>
> - won't test output be slightly different, possibly requiring new baselines?<br>
<br>
</div>It's doubtful that new baselines will be needed. This has already been<br>
dealt with for the other platforms, either by modifying the tests<br>
(i.e. turning off multisampling where it made a difference) or by<br>
uploading multiple regression images.<br>
<div class="im"><br>
> - as it's a behaviour change, we should probably put this in release notes or somewhere<br>
<br>
</div>We can announce that antialiased rendering finally comes to VTK Cocoa,<br>
just 7 years after it came to all other VTK platforms.<br>
<div class="im"><br>
> - since those flags have been there since 10.2, I imagine any GPU supporting 10.5 or later (VTK 6's requirement) will support it<br>
> - I can try this change locally, once I get my app working with VTK 6...<br>
<br>
</div>The change can easily be applied to a copy of the VTK 5 source, it's<br>
just 4 lines. I plan to test it with some of my software (which is<br>
also based on VTK 5). For rendering of wireframes it makes a huge<br>
difference to the quality of the rendering.<br>
<span class="HOEnZb"><font color="#888888"><br>
- David<br>
</font></span><div class="HOEnZb"><div class="h5">_______________________________________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.vtk.org/mailman/listinfo/vtk-developers" target="_blank">http://www.vtk.org/mailman/listinfo/vtk-developers</a><br>
<br>
</div></div></blockquote></div><br></div>