Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 1,961
    • Issues 1,961
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 97
    • Merge requests 97
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #19313
Closed
Open
Issue created Sep 09, 2019 by Cornelis Bockemühl@coboContributor

Plugin auto-load option: "no entry in PV plugin manager"

Own plugins can be written and directly integrated into a custom application. Loading them can be automatic with the REQUIRED_PLUGINS list of the paraview_client_add cmake function or inside the program using the vtkPVPluginTracker class.

In all these cases, the plugins will appear in the list of the plugin manager - as "loaded".

But this does not make too much sense because loading them is not any more required, and unloading makes not much sense (and I would even doubt whether it can be reliable to "unload" a shared library from a running program!?)

Having an an option during plugin auto-load to not show a plugin in the PV plugin manager makes sense thus and avoids filling the list with useless entries.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking