Skip to content

GitLab

  • Menu
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,846
    • Issues 1,846
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 87
    • Merge requests 87
  • 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
  • ParaView
  • ParaViewParaView
  • Issues
  • #6127
Closed
Open
Created Dec 04, 2007 by Kitware Robot@kwrobotOwner

(MARS-low) Maximum value in Set Scalar Range is checked against the minimum value on every keystroke

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


If you go to the Scalar Bar window and hit Set Scalar Range, the maximum value box is checked against the minimum value box on every keypress. This makes entering a value such as 3e7 impossible when the minimum value is 4000. After hitting the 3, the value changes to 4000.

The maximum value should only be verified when return is pressed or the box loses focus.

The workaround is to enter a dummy minimum value, enter the maximum value, then enter the correct minimum value

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