GitLab

* Moving to Apache 2.0 license
* Updated AUTHORS.txt

 * added computation of difference image to SimilarityMeasure
 * fixed possible out of bounds access in datacontainerinspectorwidget.cpp
 * added assertions to ImageRepresentationGL constructor

+ Using passthrough.vert and geometryrenderer.frag instead of the meshGeometryRenderer.vert and meshgeometryrenderer.frag
+ adding comments for the destroy function of GeometryTextureInfo and why to use it.
+ Change the depth buffer size changing part of Paint() function in datacontainerinspectorcanvas checking part.
+ Delete the commented codes which are not necessary.
+ Fix the opening braces and removing the redundant parts and only for debugging parts.
+ DVRVis and volumerendererdemo default file is revereted to the original locations.
+ Revert the shaders to the original ones.
+ StartMouseDrag and EndMouseDrag functions of the trackball are replaced with mousePress and mouseRelease.

- Delete the meshGeometryRenderer.vert and meshgeometryrenderer.frag.

Cleaned up and slightly revised GeometryData API. Cleared the way for non-value semantics. Introducing GeometryDataFactory, a collection of static methods to create standard geometric primitives.

When a new floating MDI window was created, its position was tracked
from the very beginning. This caused the window's initial move event,
generated by the show() method, to be handled by the undocking
mechanism.

This event might contain outdated position information that, in certain
cases, could trigger immediate re-docking of the floating window,
setting its pointer to 0. If this happened, then the remaining code that
configured the floating window would dereference the null pointer and
crash the application.

To fix the error, connect the floating window's signals only after it
has been fully configured. This way its initial move events are ignored.

+ Moving the geomteryshader vertex and fragment shader to application folder as they belong to it.
+ Removing unndeeded shader code.
+ Opening braces convention is considered for datacontainerinspectorcanvas.cpp and datacontainerinspectorcanvas.h  also.
+ Reusing textues for color and depth buffers instead of creating and deleting them.
+ adding gettrackball function to trackball event handler.
+ modifying resetcontent, mouse events in datacontainerinspectorcanvas class
+ using one depth buffer for datacontainerinspectorcanvas instead of one for every color buffer
+ using one frame buffer for whole datacontainerinspectorcanvas instead of one for every frame

Docked MDI windows were either drawn at at offset from the cursor or
lost mouse focus entirely when the mouse pointer left their title bars
while they were being dragged. This could happen if the mouse was moved
fast.

Start mouse drag detection in response to mouse press events. This way
mouse move events don't have to be filtered, which prevents the errors
mentioned above.

Bugs:
- Invalid Enumerator during the rendering mesh
- Problems in deleting the generated color and depth textures.
- Depth darkening still has problem :(

+ update the get function of abstractproperty.h and abstractproperty.cpp to support the const objects.

- Still sufring from invalid enumerator in meshgeomtery rendering.

+ Adding the functionality to rotate the rendered geomtery objects
+ Adding the functionality to set the rendered mesh by the user

- Still there are bugs with shader that I cannot set the color of the rendered mesh in the shader

Both MdiDockedWindow and MdiFloatingWindow intercepted not only those
move events that were sent to them directly, but also the ones that the
widgets they hosted didn't handle. This made it possible to drag both
types of windows by clicking on an empty space in their widgets and
moving the mouse.

Ignore move events whose position is inside a widget hosted in a
MdiDockedWindow or MdiFloatingWindow. This makes interacting with such
widgets more predictable.

DataContainerInspectorWidget was previously stored in a regular dock
widget, but because of its rather large dimensions it didn't fit well in
any of the docking areas.

Put DataContainerInspectorWidget in an MdiDockableWindow and add it to
the MDI area. It fits much better there, and can still be undocked if
need be.

The default implementation of activateWindow didn't forward activation
requests to MdiDockableWindow's sub-windows. Since MdiDockableWindow is
always hidden, the method was pretty much a no-op in disguise.

The overridden version of activateWindow properly forwards activation
requests, using the right method to activate the current sub-window, no
matter if it's floating or docked.

MdiDockedWindow's mouseMoveEvent method intercepted all mouse move
events when the left mouse button was pressed. This interfered with the
resizing of docked windows.

Intercept only non-resize drag events to make manipulating docked MDI
windows easier. As a side effect, moving MdiDockedWindows doesn't cause
the MDI area to re-tile its sub-windows anymore.

Both MdiDockedWindow and MdiFloatingWindow were previously regular
windows, i.e. they had minimise, maximise, and close buttons. The first
two of these buttons didn't make much sense for docked MDI windows, and
made floating MDI windows look different from undocked QDockWidgets.

Represent all MDI sub-windows as tool windows to make their subordinate
status more pronounced. For floating MDI windows this has the added
benefit of keeping them on top of the main window and minimising them
when it gets hidden.

# Adding functionality to render the mesh in the DataContainerInspectorCanvas and camera rotating around the object

MdiDockableWindow has been extracted from MdiDockArea to simplify and
better structure our MDI implementation. The new class takes care of
creating all necessary representations (docked and floating window) of
widgets added to MdiDockArea and seamlessly switching between them in
response to the user's actions (window dragging, key presses, etc).

MdiDockableWindow improves our MDI implementation in two ways:
- MdiFloatingWindow and MdiDockedWindow instances shouldn't be
  interacted with directly; they're created and disposed of as needed,
  and therefore can't be used as a handle to access and modify an MDI
  window's state; MdiDockableWindow, in contrast, fits this role
  perfectly; it manages both representations of an MDI window, and as
  a result stays around as long as at least one of them is needed
- managing state transitions of many sub-windows directly in MdiDockArea
  was becoming clumsy as signal mapping and dynamic properties were
  required; having a separate widget that only has to control the state
  of one sub-window makes the code related to state transitions much
  simpler

Closing a docked MDI subwindow caused it to disappear if the MDI area
was in SubWindowView mode, but its inactive tab could still be seen in
TabbedView mode.

If a docked MDI subwindow gets closed, hide it by removing it from the
MDI area.

The "Tools" submenu lists all standard docked tools offered by the
application (i.e. "Pipeline tree", "Pipeline properties", and "Log
viewer"), and lets the user toggle their visibility.

This commit adds a simple main menu to the application. For the time being
it only has 2 submenus, "File" and "Visualizations". The latter is created
by MdiDockArea and lets users manage the visibility and placement of
canvas windows.

# Fixing the bugs of the Color Window in the Canvas

# use 4 spaces instead of tab
# use QString operations instead of unsafe C String operations
# use static_cast casting instead of C casting

# Adding the color under the mouse cursor window and the color value in a line into the Data Inspector Widget.

# Take back the updateInfoWidget to its previous position and add a new updateColor function to just update the Color in the label.

# Add the ability to read the color when hovering the mouse into the canvas and dragging the right mouse button.

# Make a pointer from datacontainerinspectorwidget into datacontainerinspectorcanvas, as we need to call the updateInfoWidget() after updating the color.

# Make the updateInfoWidget() as public to be able to call it.

# Add the Capability to look up the color under the mouse button when one of the mouse buttons is pressed.

In its destructor, LogHighlighter first of all deleted its filter regex
explicitly, and then called `setFilterRegExp(0)`, triggering a second —
this time somewhat implicit — delete. If the filter regex pointer was
not NULL, this caused the application to crash due to a double-free.

Fix this error by not invoking `setFilterRegExp` in LogHighlighter's
destructor; the explicit delete performs the same cleanup as
`setFilterRegExp` anyways.

 * fixed 1D geometry TF editor
 * introduced OptionProperty to specify gradient computation mode
 * added s_changed signal of properties also being propagated to its shared properties
 * fixed sampling rate compensation when using adaptive sampling in simpleraycaster.frag

# use 4 spaces instead of tab
# use QString operations instead of unsafe C String operations
# use static_cast casting instead of C casting

# Adding the color under the mouse cursor window and the color value in a line into the Data Inspector Widget.

# Take back the updateInfoWidget to its previous position and add a new updateColor function to just update the Color in the label.

# Add the ability to read the color when hovering the mouse into the canvas and dragging the right mouse button.

# Make a pointer from datacontainerinspectorwidget into datacontainerinspectorcanvas, as we need to call the updateInfoWidget() after updating the color.

# Make the updateInfoWidget() as public to be able to call it.

# Add the Capability to look up the color under the mouse button when one of the mouse buttons is pressed.

Fixed missing/wrong deregistration of GeometryXdTransferFcuntionEditors when their widgets are closed (and hence the GL contexts destroyed)

Fixes -Wswitch