Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
ParaView
ParaView
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,757
    • Issues 1,757
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 67
    • Merge Requests 67
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaView
  • ParaViewParaView
  • Issues
  • #20490

Closed
Open
Opened Feb 16, 2021 by moritz-h@moritz-h

Filter with Multiple Inputs is only usable on one dataset

A custom filter with multiple inputs is sometimes disabled. I can select one dataset in the pipeline browser and the filter is disabled in the filter menu, but selecting the other dataset will allow to apply the filter.

It seems that only the "first" input is used to the check if the filter can be used on the currently selected dataset. First in means of alphabetical order of the input name. This is especially bad when the input with the "first" name is meant as optional one, and the datasets I want to look at do not even have such an input type. In this case the filter cannot be used at all.

By trying to debug this, I found a TODO note within the source for this issue: https://gitlab.kitware.com/paraview/paraview/-/blob/v5.9.0/Qt/ApplicationComponents/pqFiltersMenuReaction.cxx#L228

(I noticed that the inputs are stored in a std::map using the name as key. Therefore the "strange" behavior using the the "first" name at least has a consistent explanation.)

It would be nice if a all inputs of a filter are checked, before disabling it in the filter menu.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: paraview/paraview#20490