Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation on DAQ_move #13

Open
ddennetiere opened this issue Jun 21, 2024 · 1 comment
Open

Documentation on DAQ_move #13

ddennetiere opened this issue Jun 21, 2024 · 1 comment

Comments

@ddennetiere
Copy link

Dear PyMoDAQers,
There is an incoherence in the documentation online : the chapter 8.1.5 on DAQ_Move "the useful entry and output points that you may use in your applications", yet the plugin template repository for DAQ_move_plugins inherits DAQ_Move_base and not DAQ_move. Some of the entries in the doc (like get_continuous_actuator_value) don't exists as methods of DAQ_Move_base.

Which is it ? Should we inherit from DAQ_Move or DAQ_move_base ?

Cheers,
David

@seb5g
Copy link
Contributor

seb5g commented Jun 21, 2024

Your application (not your instrument plugin) will instantiate DAQ_Move as a part of the GUI. This guy has of course an API (that may look like the ones in a plugin) with entrypoints.

The instrument plugin class (that will be instantiated by the DAQ_Move) inherits from DAQ_Move_base whose role is to smooth out of your class all the complexity of the communication from your plugin to the GUI and inversely. The plugin focus on communicating with the instrument.

Then the app template class (or the extension template class) is here to help you construct application on the GUI level.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants