[Paraview] fontconfig warnings

I downloaded the Linux tarball from Kitware, and am getting a bazillion warnings about the fontconfig. It looks like this. Any ideas? Fontconfig warning: "/etc/fonts/conf.d/30-metric-aliases.conf", line 84: Having multiple in isn't supported and may not work as expected Fontconfig warning:

Re: [Paraview] Project polygon onto surface

On Tue, Nov 29, 2016 at 1:37 PM, Adam Dershowitz wrote: > I may mess with it some. > > FYI, I did convert my polygon to a polyline, and got it to work. But, if > I have two polylines (actually two completely separate regions) the slice > along polyline filter then

Re: [Paraview] Project polygon onto surface

I may mess with it some. FYI, I did convert my polygon to a polyline, and got it to work. But, if I have two polylines (actually two completely separate regions) the slice along polyline filter then connects them even though they should not be connected. Perhaps this is just what you

Re: [Paraview] Project polygon onto surface

Hi Adam, The Slice Along PolyLine filter looks for a vtkPolyLine type cell. But there is no reason the algorithm itself can't work with a polygon (the current implementation just doesn't look for one and may not handle it the way you want if you pass a polyline that happens to have a first and

Re: [Paraview] Paraview and Space Mouse Pro

Dear Cory, You were of right. The option was there - I needed to set the correct path for the QT directory for all modules to show up. I ignored at the beginning the QT error, and tried to see whether this plugin is available to start with. Solved. Thanks! P.S. Looking fwd. for having this

[Paraview] Segfault reading polyhedral cells xdmf3 file

Dear All, I would like to use xdmf file format for exporting polyhedral mesh results from a CFD code to be opened with Paraview. If I'm not wrong Paraview 5.2.0 should be able to read/write such kind o files. Just to understand the format of the xmf file, I've been trying to open a very easy

Re: [Paraview] Paraview and Space Mouse Pro

Dinu, I do my main development on a Mac and the option is indeed listed in the ccmake. The option variable is not defined in the top-level CMakeLists.txt file, but that doesn't mean it doesn't exist. There is some CMake code that looks in the plugins directory and creates the option variable for