Pierre Raybaut
Pierre Raybaut
It would be nice if the following dialog boxes could keep their last dimensions in user settings: - Intensity profile extraction - ROI extraction - ROI definition - New window...
This method would add a new group in the active panel ("Signals" or "Images").
DataLab currently supports 1D signals (curves) and 2D images. It would be interesting to add support for timeseries (1D signals with a time axis). This would require to add: -...
This request was initially added to DataLab's roadmap. In the meantime, a really simple plugin (an [empty plugin](https://github.com/Codra-Ingenierie-Informatique/DataLab/blob/main/plugins/examples/cdl_example_empty.py)) was added to the repository. So, is it really necessary to create...
**Description** DataLab currently employs XML-RPC for remote procedure calls, facilitating remote control capabilities such as data transmission and computation. While this system is operational, it encounters performance issues when handling...
Currently, DataLab is not designed to handle multiple instances of itself. This is because it uses a single configuration file to store the user's preferences, and it does not have...
Every single application launched with `pythonw.exe` on Windows will fail if it imports NumPy V2.0.0 or V2.0.1. This is a known bug, and it has already been fixed (hopefully it...
Currently, ROI are displayed in Signal/Image Views but in read-only mode: one can only modify ROIs using the "ROI editor" (menu entry: "Computing" > "Edit Regions of Interest..."). That is...
Currently, the ROI data model is simplistic: - It stores all the ROI associated to a signal or an image in an integer NumPy array - For images, *N* rectangular...
Here is what an *History Panel* could looks like: Main features of the *History Panel*: - Record all actions from signal/image creation to processing actions - Ability to replay a...