[vtkusers] Sharing vtkRenderer?

[Cory Quammen]

Actors store some OpenGL state in the mappers they use. While it appears to
be possible to share some kinds of OpenGL state among the different OpenGL
contexts in the render windows, VTK is not designed with this in mind.
Hence, it is safest to have different actors for different renderers.

HTH,
Cory

On Sun, Dec 6, 2015 at 10:50 PM, rakesh patil <prakeshofficial at gmail.com>
wrote:

> Hi,
>
> Thanks for your reply. It's just a question. Can't I share actors created
> by smart pointer across multiple renderers. ?
>
>
> On Sunday, December 6, 2015, Cory Quammen <cory.quammen at kitware.com>
> wrote:
>
>> Each vtkRenderWindow should have its own vtkRenderer. Also, you cannot
>> reliably share actors across different vtkRenderers, so each vtkRenderer
>> should have its own set of actors.
>>
>> - Cory
>>
>> On Sat, Dec 5, 2015 at 9:32 AM, rakesh patil <prakeshofficial at gmail.com>
>> wrote:
>>
>>> Hello users,
>>>
>>> Is it possible to share a common vtkRenderer object among multiple
>>> vtkRenderWindows? Or is it that each window should have its own renderer?
>>> What I need to do is show same actor in different windows but with
>>> different projections and viewports. Will sharing a common renderer work in
>>> this case?
>>>
>>> Thanks in advance
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the VTK FAQ at:
>>> http://www.vtk.org/Wiki/VTK_FAQ
>>>
>>> Search the list archives at: http://markmail.org/search/?q=vtkusers
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://public.kitware.com/mailman/listinfo/vtkusers
>>>
>>>
>>
>>
>> --
>> Cory Quammen
>> R&D Engineer
>> Kitware, Inc.
>>
>


-- 
Cory Quammen
R&D Engineer
Kitware, Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/vtkusers/attachments/20151206/efaf63d6/attachment.html>