Dear ParaView users,
is it possible to programmatically get the name of an object in the Pipeline
Browser? To be more specific I need to get this name from a vtkActor. I am
writing a exporter plugin (see
http://www.mail-archive.com/paraview@paraview.org/msg12939.html) and want to
name my obj
It's not possible, not from a simple exporter plugin.The exporter
lives entirely in the VTK world without any knowledge of proxies. A
unconventional approach would be explicitly make the exporter plugin
link agains the pqCore library, then you can access the
pqApplicationCore and other singletons (
don't use
SetStringMacro)
JB
-Original Message-
From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org] On
Behalf Of Utkarsh Ayachit
Sent: 17 August 2011 15:16
To: Lars Bilke
Cc: ParaView Mailliste
Subject: Re: [Paraview] Get name of object in Pipeline Browser
It's no
org [mailto:paraview-boun...@paraview.org] On
> Behalf Of Utkarsh Ayachit
> Sent: 17 August 2011 15:16
> To: Lars Bilke
> Cc: ParaView Mailliste
> Subject: Re: [Paraview] Get name of object in Pipeline Browser
>
> It's not possible, not from a simple exporter plugin.
Biddiscombe, John A.
Cc: Utkarsh Ayachit; ParaView Mailliste
Subject: Re: [Paraview] Get name of object in Pipeline Browser
Thanks for your answers!
John,
where on the gui-side do I need to pass that string? Do I need to modify the
ParaView sources? Because I only want to write a plugin which should
t understand how the name actually gets to my exporter. And because a list
of names is more general I would only pass this list to my exporter and not a
single name.
See vtkOpenSGExporter.h / .cxx on Github:
https://github.com/bilke/pv_opensg_plugin
Thank you very much for your help!!
Lars.
>
ect.
I have never tried myself so am totally unsure if it at all works, may
be totally wrong.
Takuya
Takuya OSHIMA, Ph.D.
Faculty of Engineering, Niigata University
8050 Ikarashi-Ninocho, Nishi-ku, Niigata, 950-2181, JAPAN
From: Lars Bilke
Subject: Re: [Paraview] Get name of object in Pipeline Browse
Lars
I assumed you had some kind of custom panel for your exporter. If you are just
doing file->export, then my approach won’t be suitable.
[snip]
>This is clear.
[end]
good,
...
> I assume I can get *it like this:
QList sources_and_filters =
pqApplicationCore::instance()->getServerManagerM
Now I understand your approach.
I will first try out Takuya's suggestion. Maybe that will work. If not I will
keep your thoughts in my mind and maybe reimplement the exporter as a
filter/source object.
Thanks for all your help!
Am Donnerstag, 18. August 2011 um 15:06 schrieb Biddiscombe, John
