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
Currently the "Capture output" setting is not stored anywhere. It is preserved within a session - even if another script is loaded or the database is switched. But it is reset every time Supertool is started.
I couldn't decide if the setting shoud be stored in the script file (or note) or if it should be a global config setting that would be preserved across sessions. In a way, I think it should not be tied to the script but be a "user setting".
I think excluding the setting creates an exception. Exceptions make SuperTool more difficult to document, learn and remember.
Right now, we have to post-process the Script (or "SuperTool Script" note) to remove the Category where it is desired to be more generic or not be overridden.
Also, the Capture Output is going to be desireable for specific script... but it will go unused generally. So saving with the script seems reasonable.
I think excluding the setting creates an exception. Exceptions make
SuperTool more difficult to document, learn and remember.
Right now, we have to post-process the Script (or "SuperTool Script" note)
to remove the Category where it is desired to be more generic or not be
overridden.
Also, the Capture Output is going to be desireable for specific script...
but it will go unused generally. So saving with the script seems reasonable.
—
Reply to this email directly, view it on GitHub
<#37 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEIYOXWASKKHOSG65X2PJC3ZMKWHXAVCNFSM6AAAAABK3HRK2GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRXGQYTMNZQGY>
.
You are receiving this because you commented.Message ID:
***@***.***>
Could the "Save As Note" include the "Capture output" setting ?
The text was updated successfully, but these errors were encountered: