[Paraview] [EXTERNAL] Selection ispector missing
Utkarsh Ayachit
utkarsh.ayachit at kitware.com
Wed Dec 18 09:38:06 EST 2013
That's peculiar. Thanks for digging in. I'll take a look to see if I
can spot the issue. Seems like a broken dependency or something.
On Wed, Dec 18, 2013 at 1:20 AM, Lodron, Gerald
<Gerald.Lodron at joanneum.at> wrote:
> I debugged it. The vtkSMGeneratedModules.h is not generated correctly. The header file is generated in CMakeLists.txt of SMApplication at line 131, when I print the custom command:
> message("${kwprocessXML_location}
> ${CMAKE_CURRENT_BINARY_DIR}/vtkSMGeneratedModules.h
> vtkSMDefaultModules Interface GetInterfaces
> ${resourceFiles}")
> add_custom_command(
> OUTPUT ${CMAKE_CURRENT_BINARY_DIR}/vtkSMGeneratedModules.h
> DEPENDS ${resourceFiles} kwProcessXML
> COMMAND ${kwprocessXML_location}
> ${CMAKE_CURRENT_BINARY_DIR}/vtkSMGeneratedModules.h
> vtkSMDefaultModules Interface GetInterfaces
> ${resourceFiles}
> COMMENT "Generating headers for ServerManager XMLs")
>
> It outputs a correct string:
>
> E:/Develop/win32-msvc90-build/Paraview-4.1.0/bin/$(OutDir)/vtkkwProcessXML-pv4.1.exe
> E:/Develop/win32-msvc90-build/Paraview-4.1.0/ParaViewCore/ServerManager/SMApplication/vtkSMGeneratedModules.h
> vtkSMDefaultModules Interface GetInterfaces
> D:/Develop/Source/ParaView-v4.1.0-RC1-source/ParaViewCore/ServerManager/SMApplication/Resources/filters.xml;D:/Develop/Source/ParaView-v4.1.0-RC1-source/ParaViewCore/ServerManager/SMApplication/Resources/sources.xml;D:/Develop/Source/ParaView-v4.1.0-RC1-source/ParaViewCore/ServerManager/SMApplication/Resources/readers.xml;D:/Develop/Source/ParaView-v4.1.0-RC1-source/ParaViewCore/ServerManager/SMApplication/Resources/utilities.xml;D:/Develop/Source/ParaView-v4.1.0-RC1-source/ParaViewCore/ServerManager/SMApplication/Resources/rendering.xml;D:/Develop/Source/ParaView-v4.1.0-RC1-source/ParaViewCore/ServerManager/SMApplication/Resources/views_and_representations.xml;D:/Develop/Source/ParaView-v4.1.0-RC1-source/ParaViewCore/ServerManager/SMApplication/Resources/3d_widgets.xml;D:/Develop/Source/ParaView-v4.1.0-RC1-source/ParaViewCore/ServerManager/SMApplication/Resources/internal_writers.xml;D:/Develop/Source/ParaView-v4.1.0-RC1-source/ParaViewCore/ServerManager/SMApplication/Resources/writers.xml;D:/Develop/Source/ParaView-v4.1.0-RC1-source/ParaViewCore/ServerManager/SMApplication/Resources/pythonfilter.xml
>
> So the pythonfilter.xml is correctly in the list. It seems that the command is not reexecuted from cmake or the exe is not allowed to overwrite to old header. I executed the stuff manually over cmd and now It worked and compiled. Maybe someone can reproduce that strange behaviour....
>
> Thanks for help,
> Gerald
>
> -----Ursprüngliche Nachricht-----
> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
> Gesendet: Dienstag, 17. Dezember 2013 18:28
> An: Lodron, Gerald
> Cc: paraview at paraview.org
> Betreff: Re: [Paraview] [EXTERNAL] Selection ispector missing
>
> Can you try a clean build? It's unclear exactly why this this should happen. We do build with Python 2.7* on WIndows.
>
> Utkarsh
>
> On Tue, Dec 17, 2013 at 10:06 AM, Lodron, Gerald <Gerald.Lodron at joanneum.at> wrote:
>> Hi,
>>
>> I am no python guru and since i do not need it i do not build it... I tried to build it with python now but have some troubles: I had to disable ParaviewWeb plugin (got some errors in Cmake), then I successfully generated the cmake and become the following error on compilation:
>>
>>
>> E:\Develop\win64-msvc90-build\paraview-4.1.0\ParaViewCore\ServerManage
>> r\SMApplication\vtkPVInitializer.h(301) : error C3861:
>> 'vtkSMDefaultModulespythonfilterGetInterfaces': identifier not found
>>
>>
>> Did you know where this comes from? I used python lib 2.7.3.3 and modified the find script FindPythonLibs.cmake of vtk (without modification I could not find it....).
>>
>> Thanks for help,
>> Gerald
>>
>>
>>
>> -----Ursprüngliche Nachricht-----
>> Von: Utkarsh Ayachit [mailto:utkarsh.ayachit at kitware.com]
>> Gesendet: Dienstag, 17. Dezember 2013 15:58
>> An: Lodron, Gerald
>> Cc: Moreland, Kenneth; Paraview User (paraview at paraview.org)
>> Betreff: Re: [Paraview] [EXTERNAL] Selection ispector missing
>>
>> Gerald,
>>
>> Python is becoming ever more important in ParaView. Since some functionality from FindData could indeed be kept accessible even not built with Python, I've reported a bug (http://paraview.org/Bug/view.php?id=14471). However, I'd strongly suggest enabling Python. Are you not building with Python due to build issues or site limitations?
>>
>> Utkarsh
>>
>> On Tue, Dec 17, 2013 at 8:32 AM, Lodron, Gerald <Gerald.Lodron at joanneum.at> wrote:
>>> Hi
>>>
>>>
>>>
>>> Thanks for the reply but when i click on find data dialog it tells me
>>> that I need to compile paraview with python enabled (I currently
>>> build without it, also in the past).
>>>
>>>
>>>
>>> Do I really need python for that since PV4.1, that's really annoying for me?
>>>
>>>
>>>
>>> Best regards,
>>>
>>> Gerald
>>>
>>>
>>>
>>> Von: Moreland, Kenneth [mailto:kmorel at sandia.gov]
>>> Gesendet: Montag, 16. Dezember 2013 17:05
>>> An: Lodron, Gerald; Paraview User (paraview at paraview.org)
>>> Betreff: Re: [EXTERNAL] [Paraview] Selection ispector missing
>>>
>>>
>>>
>>> Yes, there is a new way of doing this. Open the Find Data dialog box.
>>> There is a button on the top toolbar or you can go to Edit -> Find
>>> Data. In the middle of that dialog is a spreadsheet with the
>>> point/cell ids and all the fields.
>>>
>>>
>>>
>>> -Ken
>>>
>>>
>>>
>>> From: <Lodron>, Gerald <Gerald.Lodron at joanneum.at>
>>> Date: Sunday, December 15, 2013 11:20 PM
>>> To: "Paraview User (paraview at paraview.org)" <paraview at paraview.org>
>>> Subject: [EXTERNAL] [Paraview] Selection ispector missing
>>>
>>>
>>>
>>>
>>>
>>> Hello
>>>
>>>
>>>
>>> I am using the new PV 4.1.0 and cannot find the selection inspector
>>> of
>>> PV3.98 where you see the ID list of all selected points/cells and/or
>>> change the selection mode. There is only a Selection Display
>>> Inspector in the View tab of the main bar which seems to only label
>>> selected points in 3d view (since I select thousands of points this
>>> is not really sufficient for me).
>>>
>>>
>>>
>>> Is there a new way doing this?
>>>
>>>
>>>
>>> Thanks,
>>>
>>> Gerald
>>>
>>> _________________________________________________________________
>>>
>>>
>>>
>>> JOANNEUM RESEARCH Forschungsgesellschaft mbH
>>>
>>>
>>>
>>> DIGITAL - Institute for Information and Communication Technologies
>>>
>>> Steyrergasse 17, 8010 Graz, Austria
>>>
>>>
>>>
>>> phone: +43 316 876-1751
>>>
>>> fax: +43 316 8769-1751
>>>
>>> e-mail: gerald.lodron at joanneum.at
>>>
>>> web: www.joanneum.at/digital
>>>
>>> _________________________________________________________________
>>>
>>>
>>>
>>> This message and any attached files are confidential and intended
>>> solely for the addressee(s). Any publication, transmission or other
>>> use of the information by a person or entity other than the intended
>>> addressee(s) is prohibited. If you receive this in error please
>>> contact the sender and delete the material. The sender does not
>>> accept liability for any errors or omissions as a result of the transmission.
>>>
>>>
>>>
>>> Please consider the environment before printing this page.
>>>
>>>
>>>
>>>
>>>
>>>
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>
>>> Please keep messages on-topic and check the ParaView Wiki at:
>>> http://paraview.org/Wiki/ParaView
>>>
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.paraview.org/mailman/listinfo/paraview
>>>
More information about the ParaView
mailing list