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,729
    • Issues 1,729
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 66
    • Merge Requests 66
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ParaView
  • ParaViewParaView
  • Issues
  • #5513

Closed
Open
Opened Aug 14, 2007 by Kitware Robot@kwrobotOwner

Default keyframe values sometimes strange

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


Do the following

  1. Create a sphere source.
  2. Create a keyframe for the StartTheta property. The default values go from 0 to 360 (as you would expect).
  3. Create a keyframe for the Radius property. The default values for this also go from 0 to 360, which is not what one would expect.

The values for the radius are clearly taken from the start theta. If you create the radius track first, the values go from 0 to 0.5, which is much more logical.

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