Hi. Straightforward request.
Sometimes I'm monitoring something through the day and want to keep a baseline result tab open within a connection. Sometimes I'll swing through that connection and just type a quick piece of SQL and hotkey to close all tabs after. Sometimes I'll accidentally close that entire connection This happens way more often than I want it to.
The request is such that a "Close all results tabs" request ignores result tabs that we set to locked. Further (and not as important), if I attempt to close a connection tab with a locked result tab, or if I attempt to explicitly close a locked tab, Squirrel would ask if I'm sure if I want to close this locked tab, providing me an option to save my results (this last part is not important either. Just an afterthought actually).
Thanks very much! Have a great day!
Interesting. (But please post feature requests in the "Feature Requests" list, not the "Bugs" list)
So right-clicking the top handle of a result tab also should offer something like a "Toggle lock"? It then probably should show a small lock icon in the tab handle.
Now I wonder whether the meaning of a "locked" tab is that clear, because when I saw the subject "Lock result tab" I projected a request preventing the rerun icon from working on that tab (it might contain the result of an hour-long database query you don't want to rerun by accident).
With the "Close all results tabs" you mean the "Close all but this"?
I actually find your "afterthought" interesting too. Sometimes I forget to save a result which took quite some time to pull up, so if I could lock the tab while it still was waiting for the result it would prevent me closing the connection without saving the result later on.
I just tested v 3.7: currently it is not possible to make a tab sticky at that early stage ("Cannot make a cancel or error tab sticky"), which itself is not a problem and makes sense IMO, but I would guess that it would be difficult allowing a tab to be locked at that stage for the same reason.