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
When exporting a workflow as an image (e.g. using the Control + Shift + E shortcut) it would be nice to have the file name automatically populated. One idea could be, if the current workflow exists as a .bonsai, to use the full path of this file as a suggestion (replacing the extension). This would be a great quality-of-life improvement, especially when exporting the image to be used in documentation since this is currently how a graphical asset is bound to a specific workflow.
The text was updated successfully, but these errors were encountered:
When exporting a workflow as an image (e.g. using the
Control
+Shift
+E
shortcut) it would be nice to have the file name automatically populated. One idea could be, if the current workflow exists as a.bonsai
, to use the full path of this file as a suggestion (replacing the extension). This would be a great quality-of-life improvement, especially when exporting the image to be used in documentation since this is currently how a graphical asset is bound to a specific workflow.The text was updated successfully, but these errors were encountered: