MantisBT - ParaView
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0009371ParaViewFeaturepublic2009-08-05 14:392016-08-12 09:57
ReporterDave DeMarle 
Assigned ToDave DeMarle 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusclosedResolutionmoved 
PlatformOSOS Version
Product VersionDevelopment 
Target VersionFixed in Version 
Project
Topic Name
Type
Summary0009371: usability : document show filter input/output number and types
DescriptionNew users often confused about WHY a filter is greyed out.

It would be very helpful if filter input and output type number and requiredments (most of which is available from domain in servermanager xml) could be parsed and displayed somewhere. Then new users would have a clue about how to adapt their current result to make it compatible with the filter they want (point to cell/cell to point etc)

This would also be helpful for new VTK users if done at VTK level. Some people who have to refer to Doxygen page to figure out what an Algorithm does do not know enough C++ and VTK (class hierarchy, conventions - polydataalgorithm's produce polydata, FillOutputPortInformation, Constructor etc) to figure it out.
Here, doxygen parsing process should figure out whatevery it can (maybe an instantiator script could run before the parser and save a file that parser can read), to make VTK easier to use.
Steps To Reproduce
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2009-08-05 14:39Dave DeMarleNew Issue
2011-02-04 14:19David PartykaAssigned To => Dave DeMarle
2011-02-04 14:19David PartykaStatusbacklog => tabled
2011-02-04 14:19David PartykaTarget Version => 4.0
2011-06-16 13:10Zack GalbreathCategoryFeature Request => Feature
2016-08-12 09:57Kitware RobotNote Added: 0037677
2016-08-12 09:57Kitware RobotStatusbacklog => closed
2016-08-12 09:57Kitware RobotResolutionopen => moved

Notes
(0037677)
Kitware Robot   
2016-08-12 09:57   
Resolving issue as `moved`.

This issue tracker is no longer used. Further discussion of this issue may take place in the current ParaView Issues page linked in the banner at the top of this page.