Pymodaq

Viewers and Moves can now communicate using tcp/ip. A Viewer server plugin on a machine will be synchronized with any kind of pymodaq viewers using the built-in tcp/ip communication. Same for Moves

* :release:`1.5.0 <2019-07-22>`
* :bug:`3` PID models package installation added to pymodaq setup
* :release:`1.5.0 <2019-07-22>`
* :feature:`0` DAQ_Scan module's H5Saver object has now by default the option to **not** save the ROI generated data.
Only the live plots datas are still saved by default.
* :feature:`0` Viewer 1D and 2D share now the same object ROIManager to deal with their regions of interest
* :feature:`0` The pid_module can be used as an actuator within DAQ_Scan (using the preset_manager configuration)
* :feature:`0` DAQ_Scan module has now its acquisition loop within a parallel thread
* :feature:`0` pid_controller module modified to work in a parallel thread
* :bug:`0` viewer1D displayed incorrectly the legend, now fixed
* :feature:`0` pid_controller module added in daq_utils module: enable a PID loop using pymodaq modules and custom
written PID models (see documentation)
* :feature:`0` Viewers: exported data now contains axis information as a dict containing data (values of the axis),
label and units and type of data (raw or generated from a ROI)
* :feature:`0` Uniformity of the saved h5 files. Axes labels and units are added as metadata and displayed in H5Browser
* :feature:`0` creation of the H5Saver object: simplifies the data saving from pymodaq modules and adds all mandatory metadata
* :bug:`0` Navigator: double click option sends the clicked position to connected slots
* :bug:`0` DAQ_Scan: when no live plot is possible (too high dimensionality) no more scan datas are saved

Cleaning up some bugs related to new functionalities

* :feature:`0` DAQ_Move_plugins: added the method *set_position_relative_with_scaling* to have correct steps in relative motion
when scaling options are set
* :feature:`0` all modules: debug info contains now name of package, method and script line where the error has been generated
* :feature:`0` h5_browser: a right click on tree items shows a context menu. so far possibility to export current item (data)
in ascii text file (%.6e precision format).
* :feature:`0` module scanner (daq_utils.scanner) has been created. Deals with lines or area selections within any viewer2D modules. Used for DAQ_Scan
and some others plugins (for area selection if needed). Most of the scan type settings (of daq_scan) have been moved to scanner
that is now a subobject of daq_scan

Huge modification related to the scanning. Now you can select an area in one of the opened 2DViewers. This viewer could for instance be a calibrated camera referring to the x and y positions of a XY stage. The Plot2D scan 2D viewer can also be used. Say that you just did a 2D scan and now you want to scan a cross-section within!! This area can be a 2D one (rectangle, 2D scan type) or a PolyLines (linked segments, 1D scan type). Random modes and others are still available in this mode