You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Similar to #10 I would like to run optional additional code with the Logbook button.
why
Some machines have an online logbook. It would facilitate the documentation if Badger GUI can directly send its created file to this logbook
how
Idea: if option "USE_EXTERNAL_LOG" is chosen, call a function from plugins according to machine. Either extend logbook() or send_to_logbook() with the function call
issue: Where to get the current machine. Correct way is a dependency by routine. Especially if multiple logbooks per machine exists. This would be a huge alteration of the badger structure. Other option is a drop-down choice button, where the user can choose the logbook before pressing the button.
EDIT:
The logbook function can be added to interfaces.
Similar to #10 I would like to run optional additional code with the Logbook button.
why
Some machines have an online logbook. It would facilitate the documentation if Badger GUI can directly send its created file to this logbook
how
Idea: if option "USE_EXTERNAL_LOG" is chosen, call a function from plugins according to machine. Either extend logbook() or send_to_logbook() with the function call
issue: Where to get the current machine. Correct way is a dependency by routine. Especially if multiple logbooks per machine exists. This would be a huge alteration of the badger structure. Other option is a drop-down choice button, where the user can choose the logbook before pressing the button.
EDIT:
The logbook function can be added to interfaces.
From @wyrnat
The text was updated successfully, but these errors were encountered: