>>> dir(x3dExporter.SMProxy)
Methods not found on the Wrapped proxy are then forwarded to the real proxy
instance that is held by the SMProxy field.
Moreover, here is the link to the ParaView/Python documentation.
http://www.paraview.org/ParaView3/Doc/Nightly/www/py-doc/index.html
Seb
On Fri,
Hello,
Searching the past posting I found python scripts like the following from one
of the posting
exporters=servermanager.createModule("exporters")
x3dExporter=exporters.X3DExporter(FileName="test.x3d") view = GetActiveView()
x3dExporter.SetView(view) # <= NEW LINE
x3dExp
It has always been like that. We need to add support for formatting. I
remember thinking about it some, but I can't remember if I implemented
it or it still remains to be implemented -- the latter is more likely.
Utkarsh
On Fri, Mar 23, 2012 at 8:12 AM, Paul Edwards wrote:
> Hi,
>
> What formatt
Hi,
What formatting should be used when adding documentation in the server
manager XML files? I assumed it would be wiki formatting but don't think
it is working in the latest version as it all appears in one paragraph (see
calculator documentation). Is this a bug or has it always been like that
Ken,
We totally understand your frustration. For this very reason, we have
started working on an online version of a user's guide for ParaView
which will be freely available. With every release of ParaView we will
package a pdf file which will serve as the manual for that release.
You can look at
Thanks for the quick answer to my question about installing macros.
I'm writing now because I'm very unhappy about the state of the
documentation. Let me say that paraview is a great program and it
enables me to make beautiful visualizations. So I am reluctant to
criticize the developers, but it
aView/CPackParaViewConfig.cmake').
Unfortunately, ParaView documentation is missing in created ParaView
installer.
I also tried under CentOS 5, but got same results - missing
documentation. How to include ParaView documentation into my
installer?
Thanks,
Nenad.
___
Sorry, I probably wasn't clear with my original email - even though I ran
"make HTMLDocumentation" before "make install" i still got that error when
looking at the help in the GUI (even though I could see the files in the
Documnetation directory).
Regards,
Paul
On 27 January 2010 19:13, Utkarsh A
Nope, it's not just you and that's by design. We don't add an explicit
dependency to t he HTMLDocumentation target to avoid building the
documentation during development builds as that can cause building on
windows (or without rpaths).
Utkarsh
On Wed, Jan 27, 2010 at 9:42 AM, Paul Edwards wrote:
Hi,
The documentation is not workings for sources and filters - it gives the
following error:
QTextBrowser: No document for qthelp://
paraview.org/paraview/ParaViewFilters.html
I ran "make HTMLDocumentation" before "make install" and I can see the files
in the Documentation directory. Is it j
> re qch file: that's what I thought but the "make install" still copies the
> whole Documentation directory with all the html and images.
Not anymore. It used to before branding.
Utkarsh
___
Powered by www.kitware.com
Visit other Kitware open-source p
he following error when opening the documentation on my branded
>> version of ParaView:
>>
>> No Qt compressed help file (*.qch) was located.
>>
>> How do I set it up so that it will display the original paraview
>> documentation?
>>
>> Thanks,
n of ParaView:
>>
>> No Qt compressed help file (*.qch) was located.
>>
>> How do I set it up so that it will display the original paraview
>> documentation?
>>
>> Thanks,
>> Paul
>>
>
> ___
>
ed help file (*.qch) was located.
>
> How do I set it up so that it will display the original paraview
> documentation?
>
> Thanks,
> Paul
>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source
lp file (*.qch) was located.
>
> How do I set it up so that it will display the original paraview
> documentation?
>
> Thanks,
> Paul
>
>
> ___
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects
I get the following error when opening the documentation on my branded
> version of ParaView:
>
> No Qt compressed help file (*.qch) was located.
>
> How do I set it up so that it will display the original paraview
> documentation?
>
> Thanks,
> Paul
>
>
__
Hi,
I get the following error when opening the documentation on my branded
version of ParaView:
No Qt compressed help file (*.qch) was located.
How do I set it up so that it will display the original paraview
documentation?
Thanks,
Paul
17 matches
Mail list logo