Random crash that happens when we select items.
Due to image planes ?

Find 3D points of the plane to be inside the point cloud

Retrieve the points of the PC visible by the current camera on press instead of during the drag event.

On scroll, text is not correctly aligned when image is not loaded.

Use face selection to choose reference for scene scale/rotation

For some sets, some points are not correctly placed in views.

Currently, when we move a point or a vertex with the mode "Move in same plane", the first face connected to the edge/vertex is used.
We need to add a manipulator (or something else) to allow user to choose the face in which he wants to move.

Currently, all cameras are listed in the plugin.

If the plugin window is opened and a new project is loaded : crash

If metadata are not in the image file, search for an exif file.

Evolution of #48.

If thumbSize is changed on hover + wheel, the value of the slider is not update on CTRL + wheel.

Specify the modifications applied on images in their names.
(ex: add _u for undistorted images)

In ImagePlaneCmd, create two flags.

• "set" that load our custom "deffered" attribute(ie the image path) into the imageName attribute
• "unset" that clear the imageName attribute

Change camera directly on selection change and add ImagePlaneCmd to idle queue.
When the command is executed, it will retrieve the used cameras and set the right imagePlane. It may have nothing to do if too much commands have been stacked.

Warning : check image cache and unload

The user want to select a mesh and only see the cameras that can be used to texture this mesh.

Solution 1:

• retrieve the bounding box of the selected meshes

• retrieve the 3D points of the point cloud visible in this bounding box

• retrieve the cameras from the visibility of those points

• hide other cameras

  ++ only useful cameras
  -- need the visibility information to work

Solution 2:

• Retrieve all the vertices of the selected meshes

• test the intersection of thoses points with all cameras

• hide other cameras

  -- will get to much cameras
  -- more computation is required than in the solution 1
  ++ don't need the visibility information to work

Switch to "next" camera (nearest) or display a list of cameras

On reload of a scene save in .ma, there are issues with meshes.

Snap with existing edges or vertices.

When a vertex is selected, sort the camera list in order to display only the cameras in which this point has been placed in 2D.

We want to find the nearest camera from a specific camera to switch cameras easily

Currently, only the mesh created from MayaMVG are modifiable via the plugin.
Add an UI select the meshes we want to use in plugin and specify the current mesh

Visualize #70

Every triangulated must have an ID.
Display IDs of points seen by a camera in camera item

How to deal with visibility?
One point cloud file per camera?

• create a label on the mesh/cameras
• put a flag or something to be able to list the exported things
• generate the abc files

On move PC, find a display when no plan is found

Use different colors for points setted in the current view from points setted in other views.

Already exists?

If no project set :
[MayaMVG] Unexpected error (/datas/pra/openMVG-UI/src/mayaMVG/maya/MVGMayaUtil.cpp:233)
[MayaMVG] Unexpected error (/datas/pra/openMVG-UI/src/mayaMVG/core/MVGCamera.cpp:153)

On meshes created via mayaMVG

Avoid opaque quad. Use wireframe if we cannot use opacity.

Use RED color when we cannot create the face.

On camera selection from Maya, display selected camera in left MVGViewport and scroll in cameraListView.