-
Notifications
You must be signed in to change notification settings - Fork 0
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
Are the tables shared? #9
Comments
Thanks for asking the question. It shows I really need to start writing documentation... A highlighted share button indicates that the current table (of the currently selected type) is being shared with at least one more instrument. When you press that button, the popup window shows buttons for each instrument. Highlighted buttons indicate that the corresponding instrument shares the same table, meaning that editing the table will affect these instruments as well. Instruments without a table have their button disabled. If you press any of the other buttons, the table pointer is set to the table of that instrument, which may trigger deletion of the current table if it was not being shared. I the current table is being shared and you would like to clone it (so you can edit it without affecting other instruments), press the clone button at the bottom. When an instrument is copied and pasted, tables are shared if the tables were not modified since the instrument was copied. I hope this explanation makes sense. I also hope that the way I implemented table sharing makes sense too. |
Thank you for the explanation! I think it's actually a very clever and well-thought-out way to implement table sharing. It's logically structured and provides flexibility without adding unnecessary complexity. The option to clone a table for independent editing is a particularly great idea. Well done! |
Thanks, glad to hear it's clear and useful. |
I'm not sure—I seem to have trouble understanding copy/paste in general, especially in the instrument editor.
Are the tables shared with the copied instrument?
The text was updated successfully, but these errors were encountered: