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,965
    • Issues 1,965
    • 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
  • #19983
Closed
Open
Issue created Jun 10, 2020 by Axel Gerstenberger@axel.gerstenbergerReporter

Inconsistent folder name for config files on Windows and Linux

In vtkInitilizationHelper::GetUserSettingsDirectory, the folder name for the config files is set to vtkInitializationHelper::GetOrganizationName() on Windows and vtkInitializationHelper::GetApplicationName() on Linux.

I am not sure if that is on purpose or not and for Paraview, APPLICATION_NAME and ORGANIZATION are both set to "ParaView", so the difference is not visible. But when creating custom applications with a ORGANIZATION name different from APPLICATION_NAME, this seems confusing.

Attached is a patch that fixed it on PV 5.6, but the master branch still has this issue.

0900-fix_organization_name_on_windows.patch

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