bec-widgets 0.99.8__py3-none-any.whl → 0.99.9__py3-none-any.whl

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (155) hide show
  1. CHANGELOG.md +6 -6
  2. PKG-INFO +1 -1
  3. {bec_widgets-0.99.8.dist-info → bec_widgets-0.99.9.dist-info}/METADATA +1 -1
  4. {bec_widgets-0.99.8.dist-info → bec_widgets-0.99.9.dist-info}/RECORD +8 -155
  5. pyproject.toml +6 -1
  6. docs/Makefile +0 -20
  7. docs/_static/custom.css +0 -170
  8. docs/_templates/custom-class-template.rst +0 -34
  9. docs/_templates/custom-module-template.rst +0 -66
  10. docs/api_reference/api_reference.md +0 -12
  11. docs/assets/apps_48dp.svg +0 -1
  12. docs/assets/display_settings_48dp.svg +0 -1
  13. docs/assets/index_api.svg +0 -97
  14. docs/assets/index_contribute.svg +0 -76
  15. docs/assets/index_getting_started.svg +0 -66
  16. docs/assets/index_user_guide.svg +0 -67
  17. docs/assets/rocket_launch_48dp.svg +0 -1
  18. docs/assets/widget_screenshots/buttons.png +0 -0
  19. docs/assets/widget_screenshots/device_box.png +0 -0
  20. docs/assets/widget_screenshots/device_browser.png +0 -0
  21. docs/assets/widget_screenshots/device_inputs.png +0 -0
  22. docs/assets/widget_screenshots/dock_area.png +0 -0
  23. docs/assets/widget_screenshots/figure.png +0 -0
  24. docs/assets/widget_screenshots/image_widget.png +0 -0
  25. docs/assets/widget_screenshots/motor_map_widget.png +0 -0
  26. docs/assets/widget_screenshots/position_indicator.png +0 -0
  27. docs/assets/widget_screenshots/queue.png +0 -0
  28. docs/assets/widget_screenshots/ring_progress_bar.png +0 -0
  29. docs/assets/widget_screenshots/scan_controller.png +0 -0
  30. docs/assets/widget_screenshots/spinner.gif +0 -0
  31. docs/assets/widget_screenshots/status_box.png +0 -0
  32. docs/assets/widget_screenshots/text_box.png +0 -0
  33. docs/assets/widget_screenshots/toggle.png +0 -0
  34. docs/assets/widget_screenshots/waveform_widget.png +0 -0
  35. docs/assets/widget_screenshots/website.png +0 -0
  36. docs/conf.py +0 -82
  37. docs/developer/developer.md +0 -52
  38. docs/developer/introduction/concepts.md +0 -14
  39. docs/developer/introduction/contributing.md +0 -28
  40. docs/developer/introduction/introduction.md +0 -16
  41. docs/developer/introduction/useful_links.md +0 -23
  42. docs/developer/widget_development/bec_dispatcher.md +0 -143
  43. docs/developer/widget_development/widget_base_class.md +0 -171
  44. docs/developer/widget_development/widget_development.md +0 -14
  45. docs/index.md +0 -74
  46. docs/introduction/introduction.md +0 -18
  47. docs/make.bat +0 -35
  48. docs/requirements.txt +0 -12
  49. docs/user/api_reference/api_reference.md +0 -11
  50. docs/user/applications/applications.md +0 -10
  51. docs/user/customisation.md +0 -123
  52. docs/user/getting_started/BECDockArea.png +0 -0
  53. docs/user/getting_started/auto_updates.md +0 -82
  54. docs/user/getting_started/getting_started.md +0 -15
  55. docs/user/getting_started/gui_complex_gui.gif +0 -0
  56. docs/user/getting_started/installation.md +0 -33
  57. docs/user/getting_started/quick_start.md +0 -110
  58. docs/user/getting_started/video_tutorials.md +0 -17
  59. docs/user/user.md +0 -71
  60. docs/user/widgets/bec_figure/BECFigure.png +0 -0
  61. docs/user/widgets/bec_figure/bec_figure.md +0 -105
  62. docs/user/widgets/bec_status_box/bec_status_box.gif +0 -0
  63. docs/user/widgets/bec_status_box/bec_status_box.md +0 -38
  64. docs/user/widgets/buttons/buttons.md +0 -90
  65. docs/user/widgets/buttons/dark_mode_disabled.png +0 -0
  66. docs/user/widgets/buttons/dark_mode_enabled.png +0 -0
  67. docs/user/widgets/device_browser/device_browser.md +0 -36
  68. docs/user/widgets/device_browser/device_browser.png +0 -0
  69. docs/user/widgets/device_input/device_input.md +0 -100
  70. docs/user/widgets/dock_area/BECDockArea.png +0 -0
  71. docs/user/widgets/dock_area/bec_dock_area.md +0 -109
  72. docs/user/widgets/image/image_plot.gif +0 -0
  73. docs/user/widgets/image/image_widget.md +0 -84
  74. docs/user/widgets/motor_map/motor.gif +0 -0
  75. docs/user/widgets/motor_map/motor_map.md +0 -80
  76. docs/user/widgets/position_indicator/position_indicator.md +0 -69
  77. docs/user/widgets/positioner_box/positioner_box.md +0 -63
  78. docs/user/widgets/progress_bar/progress_bar.gif +0 -0
  79. docs/user/widgets/progress_bar/ring_progress_bar.md +0 -103
  80. docs/user/widgets/queue/queue.md +0 -41
  81. docs/user/widgets/scan_control/hide_scan_control.png +0 -0
  82. docs/user/widgets/scan_control/scan_control.gif +0 -0
  83. docs/user/widgets/scan_control/scan_control.md +0 -54
  84. docs/user/widgets/spinner/spinner.md +0 -68
  85. docs/user/widgets/text_box/text_box.md +0 -74
  86. docs/user/widgets/toggle/toggle.md +0 -66
  87. docs/user/widgets/waveform/bec_figure_dap.gif +0 -0
  88. docs/user/widgets/waveform/scatter_2D.gif +0 -0
  89. docs/user/widgets/waveform/w1D.gif +0 -0
  90. docs/user/widgets/waveform/waveform_widget.md +0 -132
  91. docs/user/widgets/website/website.md +0 -69
  92. docs/user/widgets/widgets.md +0 -220
  93. tests/__init__.py +0 -0
  94. tests/end-2-end/__init__.py +0 -0
  95. tests/end-2-end/conftest.py +0 -53
  96. tests/end-2-end/test_bec_dock_rpc_e2e.py +0 -298
  97. tests/end-2-end/test_bec_figure_rpc_e2e.py +0 -212
  98. tests/end-2-end/test_rpc_register_e2e.py +0 -40
  99. tests/end-2-end/test_scan_control_e2e.py +0 -71
  100. tests/references/SpinnerWidget/SpinnerWidget_darwin.png +0 -0
  101. tests/references/SpinnerWidget/SpinnerWidget_linux.png +0 -0
  102. tests/references/SpinnerWidget/SpinnerWidget_started_darwin.png +0 -0
  103. tests/references/SpinnerWidget/SpinnerWidget_started_linux.png +0 -0
  104. tests/unit_tests/__init__.py +0 -0
  105. tests/unit_tests/client_mocks.py +0 -189
  106. tests/unit_tests/conftest.py +0 -64
  107. tests/unit_tests/test_bec_connector.py +0 -80
  108. tests/unit_tests/test_bec_dispatcher.py +0 -119
  109. tests/unit_tests/test_bec_dock.py +0 -155
  110. tests/unit_tests/test_bec_figure.py +0 -270
  111. tests/unit_tests/test_bec_image.py +0 -63
  112. tests/unit_tests/test_bec_image_widget.py +0 -217
  113. tests/unit_tests/test_bec_motor_map.py +0 -282
  114. tests/unit_tests/test_bec_queue.py +0 -111
  115. tests/unit_tests/test_bec_status_box.py +0 -123
  116. tests/unit_tests/test_client_utils.py +0 -76
  117. tests/unit_tests/test_color_map_selector.py +0 -42
  118. tests/unit_tests/test_color_validation.py +0 -75
  119. tests/unit_tests/test_configs/config_device.yaml +0 -33
  120. tests/unit_tests/test_configs/config_device_no_entry.yaml +0 -27
  121. tests/unit_tests/test_configs/config_scan.yaml +0 -82
  122. tests/unit_tests/test_crosshair.py +0 -143
  123. tests/unit_tests/test_dark_mode_button.py +0 -70
  124. tests/unit_tests/test_device_browser.py +0 -83
  125. tests/unit_tests/test_device_input_base.py +0 -76
  126. tests/unit_tests/test_device_input_widgets.py +0 -178
  127. tests/unit_tests/test_error_utils.py +0 -63
  128. tests/unit_tests/test_generate_cli_client.py +0 -123
  129. tests/unit_tests/test_generate_plugin.py +0 -155
  130. tests/unit_tests/test_motor_map_widget.py +0 -194
  131. tests/unit_tests/test_msgs/__init__.py +0 -0
  132. tests/unit_tests/test_msgs/available_scans_message.py +0 -989
  133. tests/unit_tests/test_plot_base.py +0 -95
  134. tests/unit_tests/test_plugin_utils.py +0 -13
  135. tests/unit_tests/test_positioner_box.py +0 -130
  136. tests/unit_tests/test_ring_progress_bar.py +0 -337
  137. tests/unit_tests/test_rpc_register.py +0 -52
  138. tests/unit_tests/test_rpc_server.py +0 -42
  139. tests/unit_tests/test_rpc_widget_handler.py +0 -7
  140. tests/unit_tests/test_scan_control.py +0 -324
  141. tests/unit_tests/test_scan_control_group_box.py +0 -160
  142. tests/unit_tests/test_setting_dialog.py +0 -96
  143. tests/unit_tests/test_spinner.py +0 -31
  144. tests/unit_tests/test_stop_button.py +0 -27
  145. tests/unit_tests/test_text_box_widget.py +0 -54
  146. tests/unit_tests/test_toggle.py +0 -38
  147. tests/unit_tests/test_vscode_widget.py +0 -75
  148. tests/unit_tests/test_waveform1d.py +0 -712
  149. tests/unit_tests/test_waveform_widget.py +0 -462
  150. tests/unit_tests/test_website_widget.py +0 -25
  151. tests/unit_tests/test_widget_io.py +0 -90
  152. tests/unit_tests/test_yaml_dialog.py +0 -163
  153. {bec_widgets-0.99.8.dist-info → bec_widgets-0.99.9.dist-info}/WHEEL +0 -0
  154. {bec_widgets-0.99.8.dist-info → bec_widgets-0.99.9.dist-info}/entry_points.txt +0 -0
  155. {bec_widgets-0.99.8.dist-info → bec_widgets-0.99.9.dist-info}/licenses/LICENSE +0 -0
@@ -1,100 +0,0 @@
1
- (user.widgets.device_input)=
2
-
3
- # Device Input Widgets
4
-
5
- ````{tab} Overview
6
-
7
- The `Device Input Widgets` consist of two primary widgets: `DeviceLineEdit` and `DeviceComboBox`. Both widgets are designed to facilitate the selection of devices within the BEC environment, allowing users to filter, search, and select devices dynamically. These widgets are highly customizable and can be integrated into a GUI either through direct code instantiation or by using `QtDesigner`.
8
-
9
- ## DeviceLineEdit
10
- The `DeviceLineEdit` widget provides a line edit interface with autocomplete functionality for device names, making it easier for users to quickly search and select devices.
11
-
12
- ## DeviceComboBox
13
- The `DeviceComboBox` widget offers a dropdown interface for device selection, providing a more visual way to browse through available devices.
14
-
15
- ## Key Features:
16
- - **Device Filtering**: Both widgets allow users to filter devices by their class names, ensuring that only relevant devices are shown.
17
- - **Default Device Setting**: Users can set a default device to be pre-selected when the widget is initialized.
18
- - **Real-Time Autocomplete (LineEdit)**: The `DeviceLineEdit` widget supports real-time autocomplete, helping users find devices faster.
19
- - **Dropdown Selection (ComboBox)**: The `DeviceComboBox` widget displays devices in a dropdown list, making selection straightforward.
20
- - **QtDesigner Integration**: Both widgets can be added as custom widgets in `QtDesigner` or instantiated directly in code.
21
-
22
- ````
23
-
24
- ````{tab} Examples
25
-
26
- Both `DeviceLineEdit` and `DeviceComboBox` can be integrated within a GUI application through direct code instantiation or by using `QtDesigner`. Below are examples demonstrating how to create and use these widgets.
27
-
28
-
29
- ## Example 1 - Creating a DeviceLineEdit in Code
30
-
31
- In this example, we demonstrate how to create a `DeviceLineEdit` widget in code and customize its behavior.
32
-
33
- ```python
34
- from qtpy.QtWidgets import QApplication, QVBoxLayout, QWidget
35
- from bec_widgets.widgets.device_line_edit import DeviceLineEdit
36
-
37
- class MyGui(QWidget):
38
- def __init__(self):
39
- super().__init__()
40
- self.setLayout(QVBoxLayout(self)) # Initialize the layout for the widget
41
-
42
- # Create and add the DeviceLineEdit to the layout
43
- self.device_line_edit = DeviceLineEdit(device_filter="Motor")
44
- self.layout().addWidget(self.device_line_edit)
45
-
46
- # Example of how this custom GUI might be used:
47
- app = QApplication([])
48
- my_gui = MyGui()
49
- my_gui.show()
50
- app.exec_()
51
- ```
52
-
53
- ## Example 2 - Creating a DeviceComboBox in Code
54
-
55
- Similarly, here is an example of creating a `DeviceComboBox` widget in code and customizing its behavior.
56
-
57
- ```python
58
- from qtpy.QtWidgets import QApplication, QVBoxLayout, QWidget
59
- from bec_widgets.widgets.device_combo_box import DeviceComboBox
60
-
61
- class MyGui(QWidget):
62
- def __init__(self):
63
- super().__init__()
64
- self.setLayout(QVBoxLayout(self)) # Initialize the layout for the widget
65
-
66
- # Create and add the DeviceComboBox to the layout
67
- self.device_combo_box = DeviceComboBox(device_filter="Motor")
68
- self.layout().addWidget(self.device_combo_box)
69
-
70
- # Example of how this custom GUI might be used:
71
- app = QApplication([])
72
- my_gui = MyGui()
73
- my_gui.show()
74
- app.exec_()
75
- ```
76
-
77
- ## Example 3 - Setting Default Device
78
-
79
- Both `DeviceLineEdit` and `DeviceComboBox` allow you to set a default device that will be selected when the widget is initialized.
80
-
81
- ```python
82
- # Set default device for DeviceLineEdit
83
- self.device_line_edit.set_default_device("motor1")
84
-
85
- # Set default device for DeviceComboBox
86
- self.device_combo_box.set_default_device("motor2")
87
- ```
88
- ````
89
-
90
- ````{tab} API - ComboBox
91
- ```{eval-rst}
92
- .. include:: /api_reference/_autosummary/bec_widgets.cli.client.DeviceComboBox.rst
93
- ```
94
- ````
95
-
96
- ````{tab} API - LineEdit
97
- ```{eval-rst}
98
- .. include:: /api_reference/_autosummary/bec_widgets.cli.client.DeviceLineEdit.rst
99
- ```
100
- ````
Binary file
@@ -1,109 +0,0 @@
1
- (user.widgets.bec_dock_area)=
2
-
3
- # BECDockArea
4
-
5
- ````{tab} Overview
6
-
7
- [`BECDockArea`](/api_reference/_autosummary/bec_widgets.cli.client.BECDockArea) is a powerful and flexible container designed to host various widgets and docks within a grid layout. It provides an environment for organizing and managing complex user interfaces, making it ideal for applications that require multiple tools and data visualizations to be displayed simultaneously. BECDockArea is particularly useful for embedding not only visualization tools but also other interactive components, allowing users to tailor their workspace to their specific needs.
8
-
9
- - **Flexible Dock Management**: Easily add, remove, and rearrange docks within `BECDockArea`, providing a customized layout for different tasks.
10
- - **State Persistence**: Save and restore the state of the dock area, enabling consistent user experiences across sessions.
11
- - **Dock Customization**: Add docks with customizable positions, names, and behaviors, such as floating or closable docks.
12
- - **Integration with Widgets**: Integrate various widgets like [`WaveformWidget`](user.widgets.waveform_widget), [`ImageWidget`](user.widgets.image_widget), and [`MotorMapWidget`](user.widgets.motor_map) into `BECDockArea`, either as standalone tools or as part of a more complex interface.
13
-
14
- **BEC Dock Area Components Schema**
15
-
16
- ![BECDockArea.png](BECDockArea.png)
17
- ````
18
-
19
- ````{tab} Examples - CLI
20
- In the following examples, we will use `BECIPythonClient` as the main object to interact with the `BECDockArea`. These tutorials focus on how to work with the `BECDockArea` framework, such as adding and removing docks, saving and restoring layouts, and managing the docked widgets. By default the `BECDockArea` is refered as `gui` in `BECIPythonClient`. For more detailed examples of each individual component, please refer to the example sections of each individual [`widget`](user.widgets).
21
-
22
- ## Example 1 - Adding Docks to BECDockArea
23
-
24
- In this example, we will demonstrate how to add different docks to a single `BECDockArea` widget. New docks are always added to the bottom of the dock area by default; however, you can specify the position of the dock by using the `position` and `relative_to` arguments.
25
-
26
- ```python
27
- # Add a new dock with a WaveformWidget to the BECDockArea
28
- dock1 = gui.add_dock(name="Waveform Dock", widget="BECWaveformWidget")
29
-
30
- # Add a second dock with a MotorMapWidget to the BECDockArea to the right of the first dock
31
- dock2 = gui.add_dock(name="Motor Map Dock", widget="BECMotorMapWidget",relative_to="Waveform Dock", position="right")
32
-
33
- # Add a third dock with an ImageWidget to the BECDockArea, placing it on bottom of the dock area
34
- dock3 = gui.add_dock(name="Image Dock", widget="BECImageWidget")
35
- ```
36
-
37
- ```{hint}
38
- You can move docks around by dragging them with the mouse using the dock's title bar. The dock will snap to the grid layout of the dock area.
39
- ```
40
-
41
- ## Example 2 - Access of Docks in BECDockArea
42
-
43
- Docks can be accessed by their name or by the dock object. The dock object can be used to modify the dock properties or to add widgets to the dock.
44
-
45
- ```python
46
- # All docks can be accessed by their name from the panels dictionary
47
- gui.panels
48
-
49
- # Output
50
- {'Waveform Dock': <BECDock object at 0x168b983d0>,
51
- 'Motor Map Dock': <BECDock object at 0x13a969250>,
52
- 'Image Dock': <BECDock object at 0x13f267950>}
53
-
54
- # Access the dock by its name
55
- dock1 = gui.panels["Waveform Dock"]
56
-
57
- # Access the widget object of the dock
58
- waveform_widget = dock1.widget_list[0]
59
- ```
60
-
61
- ## Example 3 - Detaching and Attaching Docks in BECDockArea
62
-
63
- Docks in `BECDockArea` can be detached (floated) or reattached to the main dock area. This is useful when you want to temporarily undock a widget for better visibility or organization.
64
-
65
- ```python
66
- # Detach the dock named "Waveform Dock"
67
- gui.detach_dock(dock_name="Waveform Dock")
68
-
69
- # Docks can be also detached by the dock object
70
- dock2.detach()
71
- dock3.detach()
72
-
73
- # Docks can be individually reattached to the main dock area
74
- dock2.attach()
75
-
76
- # Reattach all floating docks to the main dock area
77
- gui.attach_all()
78
- ```
79
-
80
- ```{note}
81
- Floating docks are always returned to the original dock area if they are closed manually. Docks can also be detached by double-clicking on the dock title.
82
- ```
83
-
84
- ## Example 4 - Removing Docks from BECDockArea
85
-
86
- Docks can be removed from the dock area by their name or by the dock object. The dock object can be used to remove the dock from the dock area.
87
-
88
- ```python
89
- # Removing docks by their name
90
- gui.remove_dock(dock_name="Waveform Dock")
91
-
92
- # Removing docks by the dock object
93
- dock2.remove()
94
-
95
- # Removing all docks from the dock area
96
- gui.clear_all()
97
- ```
98
-
99
- ```{warning}
100
- When removing a dock, all widgets within the dock will be removed as well. This action cannot be undone, and all references to the dock and its widgets will be lost.
101
- ```
102
- ````
103
-
104
- ````{tab} API
105
- ```{eval-rst}
106
- .. include:: /api_reference/_autosummary/bec_widgets.cli.client.BECDockArea.rst
107
- ```
108
- ````
109
-
Binary file
@@ -1,84 +0,0 @@
1
- (user.widgets.image_widget)=
2
-
3
- # Image Widget
4
-
5
- ````{tab} Overview
6
-
7
- The Image Widget is a versatile tool designed for visualizing 2D image data, such as camera images, in real-time. Directly integrated with the `BEC` framework, it can display live data streams from connected cameras or other image sources within the current `BEC` session. The widget provides advanced customization options for color maps and scale bars, allowing users to tailor the visualization to their specific needs.
8
-
9
- ## Key Features:
10
- - **Flexible Integration**: The widget can be integrated into both [`BECFigure`](user.widgets.bec_figure) and [`BECDockArea`](user.widgets.bec_dock_area), or used as an individual component in your application through `BECDesigner`.
11
- - **Live Data Visualization**: Real-time plotting of 2D image data from cameras or other image sources, provided that a data stream is available in the BEC session.
12
- - **Customizable Color Maps and Scale Bars**: Users can customize the appearance of images with various color maps and adjust scale bars to better interpret the visualized data.
13
- - **Real-time Image Processing**: Apply real-time image processing techniques directly within the widget to enhance the quality or analyze specific aspects of the images such as rotation, log scaling, and FFT.
14
- - **Data Export**: Export visualized image data to various formats such as PNG, TIFF, or H5 for further analysis or reporting.
15
- - **Interactive Controls**: Offers interactive controls for zooming, panning, and adjusting the visual properties of the images on the fly.
16
-
17
- ![Image 2D](./image_plot.gif)
18
- ````
19
-
20
- ````{tab} Examples - CLI
21
-
22
- `ImageWidget` can be embedded in both [`BECFigure`](user.widgets.bec_figure) and [`BECDockArea`](user.widgets.bec_dock_area), or used as an individual component in your application through `BECDesigner`. However, the command-line API is the same for all cases.
23
-
24
- ## Example 1 - Adding Image Widget to BECFigure
25
-
26
- In this example, we demonstrate how to add an `ImageWidget` to a [`BECFigure`](user.widgets.bec_figure) to visualize live data from a connected camera.
27
-
28
- ```python
29
- # Add a new dock with BECFigure widget
30
- fig = gui.add_dock().add_widget('BECFigure')
31
-
32
- # Add an ImageWidget to the BECFigure
33
- img_widget = fig.image(source='eiger')
34
- img_widget.set_title("Camera Image Eiger")
35
- ```
36
-
37
- ## Example 2 - Adding Image Widget as a Dock in BECDockArea
38
-
39
- Adding `ImageWidget` into a [`BECDockArea`](user.widgets.bec_dock_area) is similar to adding any other widget. The widget has the same API as the one in [`BECFigure`](user.widgets.bec_figure); however, as an independent widget outside [`BECFigure`](user.widgets.bec_figure), it has its own toolbar, allowing users to configure the widget without needing CLI commands.
40
-
41
- ```python
42
- # Add an ImageWidget to the BECDockArea
43
- img_widget = gui.add_dock().add_widget('BECImageWidget')
44
-
45
- # Visualize live data from a camera with range from 0 to 100
46
- img_widget.image(source='eiger')
47
- img_widget.set_vrange(vmin=0, vmax=100)
48
- ```
49
-
50
- ## Example 3 - Customizing Image Display
51
-
52
- This example demonstrates how to customize the color map and scale bar for an image being visualized in an `ImageWidget`.
53
-
54
- ```python
55
- # Set the color map and adjust the scale bar range
56
- img_widget.set_colormap("viridis")
57
- img_widget.set_vrange(vmin=10, vmax=200)
58
- ```
59
-
60
- ## Example 4 - Real-time Image Processing
61
-
62
- The `ImageWidget` provides real-time image processing capabilities, such as rotating, scaling, and applying FFT to the displayed images. The following example demonstrates how to rotate an image by 90 degrees, transpose it, and apply FFT.
63
-
64
- ```python
65
- # Rotate the image by 90 degrees
66
- img_widget.set_rotation(deg_90=1)
67
-
68
- # Transpose the image
69
- img_widget.set_transpose(enable=True)
70
-
71
- # Apply FFT to the image
72
- img_widget.set_fft(enable=True)
73
-
74
- # Set the logarithmic scale for the image display
75
- img_widget.set_log(enable=True)
76
- ```
77
-
78
- ````
79
-
80
- ````{tab} API
81
- ```{eval-rst}
82
- .. include:: /api_reference/_autosummary/bec_widgets.cli.client.BECImageWidget.rst
83
- ```
84
- ````
Binary file
@@ -1,80 +0,0 @@
1
- (user.widgets.motor_map)=
2
-
3
- # Motor Map Widget
4
-
5
- ````{tab} Overview
6
-
7
- The Motor Map Widget is a specialized tool for tracking and visualizing the positions of motors in real-time. This widget is crucial for applications requiring precise alignment and movement tracking during scans. It provides an intuitive way to monitor motor trajectories, ensuring accurate positioning throughout the scanning process.
8
-
9
- ## Key Features:
10
- - **Flexible Integration**: The widget can be integrated into both [`BECFigure`](user.widgets.bec_figure) and [`BECDockArea`](user.widgets.bec_dock_area), or used as an individual component in your application through `BECDesigner`.
11
- - **Real-time Motor Position Visualization**: Tracks motor positions in real-time and visually represents motor trajectories.
12
- - **Customizable Visual Elements**: The appearance of all widget components is fully customizable, including scatter size and background values.
13
- - **Interactive Controls**: Interactive controls for zooming, panning, and adjusting the visual properties of motor trajectories on the fly.
14
-
15
- ![MotorMap](./motor.gif)
16
- ````
17
-
18
- ````{tab} Examples CLI
19
- `MotorMapWidget` can be embedded in both [`BECFigure`](user.widgets.bec_figure) and [`BECDockArea`](user.widgets.bec_dock_area), or used as an individual component in your application through `BECDesigner`. However, the command-line API is the same for all cases.
20
-
21
- ## Example 1 - Adding Motor Map Widget to BECFigure
22
-
23
- In this example, we will demonstrate how to add two different `MotorMapWidgets` into a single [`BECFigure`](user.widgets.bec_figure) widget.
24
-
25
- ```python
26
- # Add new dock with BECFigure widget
27
- fig = gui.add_dock().add_widget('BECFigure')
28
-
29
- # Add two WaveformWidgets to the BECFigure
30
- mm1 = fig.motor_map(motor_x='samx', motor_y='samy')
31
- mm2 = fig.motor_map(motor_x='aptrx', motor_y='aptry',new=True)
32
- ```
33
-
34
- ## Example 2 - Adding Motor Map Widget as a Dock in BECDockArea
35
-
36
- Adding `MotorMapWidget` into a [`BECDockArea`](user.widgets.bec_dock_area) is similar to adding any other widget. The widget has the same API as the one in BECFigure; however, as an independent widget outside BECFigure, it has its own toolbar, allowing users to configure the widget without needing CLI commands.
37
-
38
- ```python
39
- # Add new MotorMaps to the BECDockArea
40
- mm1 = gui.add_dock().add_widget('BECMotorMapWidget')
41
- mm2 = gui.add_dock().add_widget('BECMotorMapWidget')
42
-
43
- # Add signals to the MotorMaps
44
- mm1.change_motors(motor_x='samx', motor_y='samy')
45
- mm2.change_motors(motor_x='aptrx', motor_y='aptry')
46
- ```
47
-
48
- ## Example 3 - Customizing Motor Map Display
49
-
50
- The `MotorMapWidget` allows customization of its visual elements to better suit the needs of your application. Below is an example of how to adjust the scatter size, set background values, and limit the number of points displayed from the position buffer.
51
-
52
- ```python
53
- # Set scatter size
54
- mm1.set_scatter_size(scatter_size=5)
55
-
56
- # Set background value
57
- mm1.set_background_value(background_value=0)
58
-
59
- # Limit the number of points displayed and saved in the position buffer
60
- mm1.set_max_points(max_points=500)
61
- ```
62
-
63
- ## Example 4 - Changing Motors and Resetting History
64
-
65
- You can dynamically change the motors being tracked and reset the history of the motor trajectories during the session.
66
-
67
- ```python
68
- # Reset the history of motor movements
69
- mm1.reset_history()
70
-
71
- # Change the motors being tracked
72
- mm1.change_motors(motor_x='aptrx', motor_y='aptry')
73
- ```
74
- ````
75
-
76
- ````{tab} API
77
- ```{eval-rst}
78
- .. include:: /api_reference/_autosummary/bec_widgets.cli.client.BECMotorMap.rst
79
- ```
80
- ````
@@ -1,69 +0,0 @@
1
- (user.widgets.position_indicator)=
2
-
3
- # Position Indicator Widget
4
-
5
- ````{tab} Overview
6
-
7
- The [`PositionIndicator`](/api_reference/_autosummary/bec_widgets.cli.client.PositionIndicator) widget is a simple yet effective tool for visually indicating the position of a motor within its set limits. This widget is particularly useful in applications where it is important to provide a visual cue of the motor's current position relative to its minimum and maximum values. The `PositionIndicator` can be easily integrated into your GUI application either through direct code instantiation or by using `QtDesigner`.
8
-
9
- ## Key Features:
10
- - **Position Visualization**: Displays the current position of a motor on a linear scale, showing its location relative to the defined limits.
11
- - **Customizable Range**: The widget allows you to set the minimum and maximum range, adapting to different motor configurations.
12
- - **Real-Time Updates**: Responds to real-time updates, allowing the position indicator to move dynamically as the motor's position changes.
13
- - **QtDesigner Integration**: Can be added directly in code or through `QtDesigner`, making it adaptable to various use cases.
14
-
15
- ````
16
-
17
- ````{tab} Examples
18
-
19
- The `PositionIndicator` widget can be embedded within a GUI application through direct code instantiation or by using `QtDesigner`. Below are examples demonstrating how to create and use the `PositionIndicator` widget.
20
-
21
- ## Example 1 - Creating a Position Indicator in Code
22
-
23
- In this example, we demonstrate how to create a `PositionIndicator` widget in code and connect it to a slider to simulate position updates.
24
-
25
- ```python
26
- from qtpy.QtWidgets import QApplication, QSlider, QVBoxLayout, QWidget
27
- from bec_widgets.widgets.position_indicator import PositionIndicator
28
-
29
- app = QApplication([])
30
-
31
- # Create the PositionIndicator widget
32
- position_indicator = PositionIndicator()
33
-
34
- # Create a slider to simulate position changes
35
- slider = QSlider(Qt.Horizontal)
36
- slider.valueChanged.connect(lambda value: position_indicator.on_position_update(value / 100))
37
-
38
- # Create a layout and add the widgets
39
- layout = QVBoxLayout()
40
- layout.addWidget(position_indicator)
41
- layout.addWidget(slider)
42
-
43
- # Set up the main widget
44
- widget = QWidget()
45
- widget.setLayout(layout)
46
- widget.show()
47
-
48
- app.exec_()
49
- ```
50
-
51
- ## Example 2 - Setting the Range for the Position Indicator
52
-
53
- You can set the minimum and maximum range for the position indicator to reflect the actual limits of the motor.
54
-
55
- ```python
56
- # Set the range for the position indicator
57
- position_indicator.set_range(min_value=0, max_value=200)
58
- ```
59
-
60
- ## Example 3 - Integrating the Position Indicator in QtDesigner
61
-
62
- The `PositionIndicator` can be added to your GUI layout using `QtDesigner`. Once added, you can connect it to the motor's position updates using the `on_position_update` slot.
63
-
64
- ```python
65
- # Example: Updating the position in a QtDesigner-based application
66
- self.position_indicator.on_position_update(new_position_value)
67
- ```
68
-
69
- ````
@@ -1,63 +0,0 @@
1
- (user.widgets.positioner_box)=
2
-
3
- # Positioner Box Widget
4
-
5
- ````{tab} Overview
6
-
7
- The [`PositionerBox`](/api_reference/_autosummary/bec_widgets.cli.client.PositionerBox) widget provides a graphical user interface to control a positioner device within the BEC environment. This widget allows users to interact with a positioner by setting setpoints, tweaking the motor position, and stopping motion. The device selection can be done via a small button under the device label, through `QtDesigner`, or by using the command line interface (CLI). This flexibility makes the `PositionerBox` an essential tool for tasks involving precise position control.
8
-
9
- ## Key Features:
10
- - **Device Selection**: Easily select a positioner device by clicking the button under the device label or by configuring the widget in `QtDesigner`.
11
- - **Setpoint Control**: Directly set the positioner’s target setpoint and issue movement commands.
12
- - **Tweak Controls**: Adjust the motor position incrementally using the tweak left/right buttons.
13
- - **Real-Time Feedback**: Monitor the device’s current position and status, with live updates on whether the device is moving or idle.
14
- - **Flexible Integration**: Can be integrated into a GUI through `BECDockArea` or used as a standalone component in `QtDesigner`.
15
- ````
16
-
17
- ````{tab} Examples
18
-
19
- The `PositionerBox` widget can be integrated within a GUI application either through direct code instantiation or by using `QtDesigner`. Below are examples demonstrating how to create and use the `PositionerBox` widget.
20
-
21
- ## Example 1 - Creating a PositionerBox in Code
22
-
23
- In this example, we demonstrate how to create a `PositionerBox` widget in code and configure it for a specific device.
24
-
25
- ```python
26
- from qtpy.QtWidgets import QApplication, QVBoxLayout, QWidget
27
- from bec_widgets.widgets.positioner_box import PositionerBox
28
-
29
- class MyGui(QWidget):
30
- def __init__(self):
31
- super().__init__()
32
- self.setLayout(QVBoxLayout(self)) # Initialize the layout for the widget
33
-
34
- # Create and add the PositionerBox to the layout
35
- self.positioner_box = PositionerBox(device="motor1")
36
- self.layout().addWidget(self.positioner_box)
37
-
38
- # Example of how this custom GUI might be used:
39
- app = QApplication([])
40
- my_gui = MyGui()
41
- my_gui.show()
42
- app.exec_()
43
- ```
44
-
45
- ## Example 2 - Selecting a Device via GUI
46
-
47
- Users can select the positioner device by clicking the button under the device label, which opens a dialog for device selection.
48
-
49
- ## Example 3 - Customizing PositionerBox in QtDesigner
50
-
51
- The `PositionerBox` widget can be added to a GUI through `QtDesigner`. Once integrated, you can configure the default device and customize the widget’s appearance and behavior directly within the designer.
52
-
53
- ```python
54
- # After adding the widget to a form in QtDesigner, you can configure the device:
55
- self.positioner_box.set_positioner("motor2")
56
- ```
57
- ````
58
-
59
- ````{tab} API
60
- ```{eval-rst}
61
- .. include:: /api_reference/_autosummary/bec_widgets.cli.client.PositionerBox.rst
62
- ```
63
- ````
@@ -1,103 +0,0 @@
1
- (user.widgets.ring_progress_bar)=
2
-
3
- # Ring Progress Bar
4
-
5
- ````{tab} Overview
6
-
7
- The [`Ring Progress Bar`](/api_reference/_autosummary/bec_widgets.cli.client.RingProgressBar) widget is a circular progress bar designed to visualize the progress of tasks in a clear and intuitive manner. This widget is particularly useful in applications where task progress needs to be represented as a percentage. The `Ring Progress Bar` can be controlled directly via its API or can be hooked up to track the progress of a device readback or scan, providing real-time visual feedback.
8
-
9
- ## Key Features:
10
- - **Circular Progress Visualization**: Displays a circular progress bar to represent task completion.
11
- - **Device and Scan Integration**: Hooks into device readbacks or scans to automatically update the progress bar based on real-time data.
12
- - **Multiple Rings**: Supports multiple progress rings within the same widget to track different tasks in parallel.
13
- - **Customizable Visual Elements**: Allows customization of colors, line widths, and other visual elements for each progress ring.
14
-
15
- ![RingProgressBar](./progress_bar.gif)
16
-
17
- ````
18
-
19
- ````{tab} Example
20
-
21
- ## Example 1 - Adding Ring Progress Bar to BECDockArea
22
-
23
- In this example, we demonstrate how to add a `RingProgressBar` widget to a `BECDockArea` to visualize the progress of a task.
24
-
25
- ```python
26
- # Add a new dock with a RingProgressBar widget
27
- progress = gui.add_dock().add_widget("RingProgressBar")
28
-
29
- # Customize the size of the progress ring
30
- progress.set_line_widths(20)
31
- ```
32
-
33
- ## Example 2 - Adding Multiple Rings to Track Parallel Tasks
34
-
35
- By default, the `RingProgressBar` widget displays a single ring. You can add additional rings to track multiple tasks simultaneously.
36
-
37
- ```python
38
- # Add a second ring to the RingProgressBar
39
- progress.add_ring()
40
-
41
- # Customize the rings
42
- progress.rings[0].set_line_widths(20) # Set the width of the first ring
43
- progress.rings[1].set_line_widths(10) # Set the width of the second ring
44
- ```
45
-
46
- ## Example 3 - Integrating with Device Readback and Scans
47
-
48
- The `RingProgressBar` can automatically update based on the progress of scans or device readbacks. This example shows how to set up the progress rings to reflect these updates.
49
-
50
- ```python
51
- # Set the first ring to update based on scan progress
52
- progress.rings[0].set_update("scan")
53
-
54
- # Set the second ring to update based on a device readback (e.g., samx)
55
- progress.rings[1].set_update("device", "samx")
56
- ```
57
-
58
- ## Example 4 - Customizing Visual Elements of the Rings
59
-
60
- The `RingProgressBar` widget offers various customization options, such as changing colors, line widths, and the gap between rings.
61
-
62
- ```python
63
- # Set the color of the first ring to blue
64
- progress.rings[0].set_color("blue")
65
-
66
- # Set the background color of the second ring
67
- progress.rings[1].set_background("gray")
68
-
69
- # Adjust the gap between the rings
70
- progress.set_gap(5)
71
-
72
- # Set the diameter of the progress bar
73
- progress.set_diameter(150)
74
- ```
75
-
76
- ## Example 5 - Manual Updates and Precision Control
77
-
78
- While the `RingProgressBar` supports automatic updates, you can also manually control the progress and set the precision for each ring.
79
-
80
- ```python
81
- # Disable automatic updates and manually set the progress value
82
- progress.enable_auto_updates(False)
83
- progress.rings[0].set_value(75) # Set the first ring to 75%
84
-
85
- # Set precision for the progress display
86
- progress.set_precision(2) # Display progress with two decimal places
87
-
88
-
89
- # Setting multiple rigns with different values
90
- progress.set_number_of_bars(3)
91
-
92
- # Set the values of the rings to 50, 75, and 25 from outer to inner ring
93
- progress.set_value([50, 75, 25])
94
- ```
95
-
96
- ````
97
-
98
- ````{tab} API
99
- ```{eval-rst}
100
- .. include:: /api_reference/_autosummary/bec_widgets.cli.client.RingProgressBar.rst
101
- ```
102
- ````
103
-
@@ -1,41 +0,0 @@
1
- (user.widgets.bec_queue)=
2
-
3
- # BEC Queue Widget
4
-
5
- ````{tab} Overview
6
-
7
- The [`BEC Queue Widget`](/api_reference/_autosummary/bec_widgets.cli.client.BECQueue) provides a real-time display of the BEC scan queue, allowing users to monitor and track the status of ongoing and pending scans. The widget automatically updates to reflect the current state of the scan queue, displaying critical information such as scan numbers, types, and statuses. This widget is particularly useful for users who need to manage and oversee multiple scans in the BEC environment.
8
-
9
- ## Key Features:
10
- - **Real-Time Queue Monitoring**: Displays the current state of the BEC scan queue, with automatic updates as the queue changes.
11
- - **Detailed Scan Information**: Provides a clear view of scan numbers, types, and statuses, helping users track the progress and state of each scan.
12
- - **Interactive Table Layout**: The queue is presented in a table format, with customizable columns that stretch to fit the available space.
13
- - **Flexible Integration**: The widget can be integrated into both [`BECDockArea`](user.widgets.bec_dock_area) and used as an individual component in your application through `QtDesigner`.
14
-
15
- ````
16
-
17
- ````{tab} Examples
18
-
19
- The `BEC Queue Widget` can be embedded within a [`BECDockArea`](user.widgets.bec_dock_area) or used as an individual component in your application through `QtDesigner`. Below are examples demonstrating how to create and use the `BEC Queue Widget`.
20
-
21
- ## Example 1 - Adding BEC Queue Widget to BECDockArea
22
-
23
- In this example, we demonstrate how to add a `BECQueue` widget to a `BECDockArea`, allowing users to monitor the BEC scan queue directly from the GUI.
24
-
25
- ```python
26
- # Add a new dock with a BECQueue widget
27
- bec_queue = gui.add_dock().add_widget("BECQueue")
28
- ```
29
-
30
- ```{hint}
31
- The `BECQueue` widget automatically updates as the scan queue changes, providing real-time feedback on the status of each scan.
32
- Once the widget is added, it will automatically display the current scan queue
33
- ```
34
-
35
- ````
36
-
37
- ````{tab} API
38
- ```{eval-rst}
39
- .. include:: /api_reference/_autosummary/bec_widgets.cli.client.BECQueue.rst
40
- ```
41
- ````