Burlen,
That's a good point. Mind reporing a bug for this? Upgrading the
ParaViewPlugins.cmake file has been on my wish list for a while now.
They macros have never been revisited or cleanup since their
inception. I would like to collect such feature requests so we can
take all such things into c
I thought I fixed all of the reader and writer plugins in the
ParaView/Plugins directory to be server side only, unless they needed to
modify the GUI (maybe the SLAC reader did). I didn't check on any of the
other plugins though.
On Mon, Jan 20, 2014 at 9:51 AM, Utkarsh Ayachit <
utkarsh.ayac...@
Nicholas,
There's not much to it once you have the vtkExporter subclass ready.
For making that exporter available in ParaView, you create a XML
putting the definition under the "exporters" group. The proxy
definition should use a
(http://www.paraview.org/ParaView3/Doc/Nightly/www/cxx-doc/classvtkS
You can tell the "CubeAxis" to use untransformed original data bounds.
For that, click of the "Edit" button next to the "Show Axis" check
box, which will pop-up the cube-axis editor dialog. Now for the axis
of interest, check "Original Bounds as Range". Note this must be
checked separately for eac
I am not sure I understand what you're trying to do. Do you want to
access the pixel buffer to "read" the image rendered by ParaView or
"write" to the image rendered in ParaView?
Utkarsh
On Mon, Dec 30, 2013 at 11:31 AM, Richard Townsend
wrote:
> Hi folks —
>
> Newbie here. I’m wondering whethe
Dear Giuseppe,
Yes I remember the issue. I have a test data set, and I just tested it. It
works with version 4.1. Send me your data set and I'll look at what we
might have missed.
Best regards,
Patrick
On Mon, Jan 20, 2014 at 8:37 AM, Giuseppe Pitton
wrote:
> Dear Patrick,
> I am a ParaView us
Hi there,
I've installed ParaviewWeb from source and configured apache to work with
jetty. I think I've done every configuration according to the tutorials.
But everytime I try to open DataProber application I face with the
following error in Jetty console output:
Jan 20, 2014 7:50:18 PM
> com.kit
The web socket forwarding should be handle by Apache at that point and it
seems to be done by Jetty?
In your jetty configuration, the session URL might not be valid when using
Apache as a front-end.
Moreover, which Apache setup did you used? 2.4+ like for the EC2 Amazon
documentation or the old on
