[Paraview] Filter suddenly stopped working "did not create output for port 0"

2017-12-05 Thread Chris Marsh
Hi, I have a filter that decodes a posix string from a pvd file into a datetime format. This has worked well, however with the newest paraview I get the error ERROR: In ParaView-v5.4.1/VTK/Common/ExecutionModel/vtkDemandDrivenPipeline.cxx, line 672 vtkPVCompositeDataPipeline (0x60c0001ad9e0):

Re: [Paraview] Segfault with 'Hover Cells' over 3d glyphs

2017-12-05 Thread Wyatt Spear
I just tried it with my larger data set (easier to select individual cells) and it crashed with 5.4.1. I'm not sure what the difference was with the smaller data set in 5.4.1 that let it work. =Wyatt On Tue, Dec 5, 2017 at 12:00 PM, David E DeMarle wrote: > Crashes for

Re: [Paraview] Segfault with 'Hover Cells' over 3d glyphs

2017-12-05 Thread David E DeMarle
Crashes for me. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Dec 5, 2017 at 2:59 PM, Wyatt Spear wrote: > Nope, 5.4.1 seems to work correctly. > =Wyatt > > On Tue, Dec 5, 2017 at 11:29 AM,

Re: [Paraview] Segfault with 'Hover Cells' over 3d glyphs

2017-12-05 Thread Wyatt Spear
Nope, 5.4.1 seems to work correctly. =Wyatt On Tue, Dec 5, 2017 at 11:29 AM, David E DeMarle wrote: > The output warnings you are seeing are unrelated and fixed in master. > > Can reproduce the bug with 5.4.1 binary on linux. > > > > > David E DeMarle > Kitware, Inc. >

Re: [Paraview] Segfault with 'Hover Cells' over 3d glyphs

2017-12-05 Thread David E DeMarle
The output warnings you are seeing are unrelated and fixed in master. Can reproduce the bug with 5.4.1 binary on linux. David E DeMarle Kitware, Inc. Principal Engineer 21 Corporate Drive Clifton Park, NY 12065-8662 Phone: 518-881-4909 On Tue, Dec 5, 2017 at 2:10 PM, Wyatt Spear

[Paraview] Segfault with 'Hover Cells' over 3d glyphs

2017-12-05 Thread Wyatt Spear
Greetings, I'm using the SC17 preview of 5.5 of ParaView. I first noticed this error with my own dataset but it appears with the simple test.csv I've included. To reproduce the segfault: Load the attached (or presumably any) CSV points file. Run the TableToPoints filter. Assign the X/Y/Z column

Re: [Paraview] [EXTERNAL] Re: background color not saved in state

2017-12-05 Thread Cory Quammen
Great, thanks Alan. Cory On Tue, Dec 5, 2017 at 12:58 PM, Scott, W Alan wrote: > Cory, > I've replicated this one. It is still in master. I wrote it up a while ago > here: https://gitlab.kitware.com/paraview/paraview/issues/16879. I will > update the bug with exactly

Re: [Paraview] [EXTERNAL] Re: background color not saved in state

2017-12-05 Thread Scott, W Alan
Cory, I've replicated this one. It is still in master. I wrote it up a while ago here: https://gitlab.kitware.com/paraview/paraview/issues/16879. I will update the bug with exactly how to replicate. Alan > -Original Message- > From: ParaView [mailto:paraview-boun...@paraview.org] On

Re: [Paraview] background color not saved in state

2017-12-05 Thread Heiland, Randy
Strange. I just did the same steps and when I reload, it momentarily flashes the background in black (as I’d saved it), but then switches to white. ParaView-5.4.1-Qt5-OpenGL2-MPI-OSX10.8-64bit.dmg > On Dec 5, 2017, at 8:58 AM, Cory Quammen wrote: > > Hmm, I can't

Re: [Paraview] cygwin installation

2017-12-05 Thread Ben Boeckel
On Tue, Dec 05, 2017 at 10:20:50 +1300, Zohar Levi via ParaView wrote: > To be more specific, I'm building paraview 5.4.1 (gcc on cygwin), and I > get the following errors: > > $ make > [� 0%] Built target vtkWrappingTools > [� 0%] Built target vtkWrapHierarchy > [� 0%] Building CXX object >

Re: [Paraview] background color not saved in state

2017-12-05 Thread Cory Quammen
Hmm, I can't reproduce with the following: * Start ParaView * Add Wavelet * Change background color. * Save state, reset the session, and reload the state. Can you give step-by-step instructions for how to reproduce? By the way, if you wish to discuss in the issue tracker, the original Mantis

Re: [Paraview] Optimus and Windows 10

2017-12-05 Thread Aron Helser
Yes, that Intel driver bug is known to affect ParaView: https://gitlab.kitware.com/paraview/paraview/issues/17499 Regards, Aron On Tue, Dec 5, 2017 at 6:40 AM, Jonathan Borduas < jonathan.bord...@caboma.com> wrote: > Was the laptop running with the intel gpu ? If so, it might be related to > an

[Paraview] background color not saved in state

2017-12-05 Thread Heiland, Randy
Is this the expected behavior? Related: https://www.paraview.org/Bug/bug_relationship_graph.php?bug_id=8722=relation thanks, Randy ___ Powered by www.kitware.com Visit other Kitware open-source projects at

Re: [Paraview] Optimus and Windows 10

2017-12-05 Thread Jonathan Borduas
Was the laptop running with the intel gpu ? If so, it might be related to an Intel driver bug that was reported on the QT and Intel websites. https://bugreports.qt.io/browse/QTBUG-40485 https://software.intel.com/en-us/node/744153 Jonathan Borduas _ From: Paul Melis

Re: [Paraview] Optimus and Windows 10

2017-12-05 Thread Dani Schmid
Hi, I have the same problem on my laptop. Same kind of setup, i.e. integrated Intel and dedicated GeForce graphics card. 'will check if your solution also solves it here. Cheers, Dani On Tue, Dec 5, 2017 at 10:06 AM, Paul Melis wrote: > Hi, > > In our paraview course

[Paraview] Optimus and Windows 10

2017-12-05 Thread Paul Melis
Hi, In our paraview course two weeks ago we had a student that had trouble running Paraview 5.4.1 (official windows 64-bit binaries) under windows 10. The symptoms were that the main menu bar was invisible and that the mouse cursor did not match up with the position of the click event,