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
  • #16052
Closed
Open
Issue created Mar 30, 2016 by Kitware Robot@kwrobotOwner

Rescale to Custom Range should be sticky

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


The Rescale to Custom Range should be sticky within a session. In other words, as an analyst explores their data, and looks at different variables, min and max set with Rescale to Custom Range should persist.

A great example from the paraview e-mail list:

  • Local server, Linux, 5.0.1
  • Open disk_out_ref.exo. All vars on. Apply.
  • Color by V. Rescale to Custom Range, use min=10, max=16.
  • Color by Temp.
  • Color by V. Min and max have been reset. This should not have happened.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking