[vtkusers] [vtk-developers] Call to Render on WM_PAINT in vtkWin32RenderWindowInteractor

[Ken Martin]

No clue why it has a paint, but if everything passes with it removed then I
think it would be a good fix - Ken



Ken Martin PhD

Chairman & CFO

Kitware Inc.

28 Corporate Drive

Clifton Park NY 12065

ken.martin at kitware.com

919 869-8871 (w)





This communication, including all attachments, contains confidential and
legally privileged information, and it is intended only for the use of the
addressee.  Access to this email by anyone else is unauthorized. If you are
not the intended recipient, any disclosure, copying, distribution or any
action taken in reliance on it is prohibited and may be unlawful. If you
received this communication in error please notify us immediately and
destroy the original message.  Thank you.



*From:* vtk-developers [mailto:vtk-developers-bounces at vtk.org] *On Behalf
Of *Xabi Riobe
*Sent:* Friday, October 2, 2015 8:43 AM
*To:* VTK Users; VTK Developers
*Subject:* [vtk-developers] Call to Render on WM_PAINT in
vtkWin32RenderWindowInteractor



Hi,



Does someone know why in vtkWin32RenderWindowInteractor::vtkHandleMessage2
there is the Render() call on WM_PAINT:



case WM_PAINT:

  me->Render();

  return CallWindowProc(me->OldProc,hWnd,uMsg,wParam,lParam);

  break;



since CallWindowProc will lead to vtkWin32OpenGLRenderWindow::MessageProc
that performs the rendering on WM_PAINT



So we have a double rendering that can be slow...



For example, resize a render window and you can see this happening.



Thanks for any info about that
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20151023/67db418d/attachment.html>