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,960
    • Issues 1,960
    • 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

Gitlab will be updated February 2nd, between 8am and 9am EST (UTC-5). Gitlab will be offline during that time.

  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #19257
Closed
Open
Issue created Aug 15, 2019 by W. Alan Scott@wascottMaintainer

View/ Lights - Move to Camera makes ParaView unstable

Let me start by saying that to a light, "Move to Camera" means move the light to the current camera location. This bug assumes that "Move to Camera" is NOT really "Move Camera".

  • Linux, 5.7.0-RC2, builtin server.
  • Sources/ Cone. Apply.
  • Not needed, but rotate counter clockwise 90 degrees.
  • View/ Light Inspector.
  • Add Light.
  • Move To Camera.

ParaView is now really weird.

  • The mouse has picked up a hand icon, rather than the default pointer.
  • You are no longer moving the object with the left mouse button! This can be stopped by using the right mouse button, then the left.

This needs to be fixed.

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