"Kill switch" option ideas
-
@vectoradmin I was mentioning a little while back about including a "kill-switch" of sorts to bigger operations for in the cases where they would otherwise freeze up the entire program and require a force quit and restart.
Another thought ran through my head just now as I was thinking about it again and I wanted to get it written down and in conversation.
I think this was for browsers - maybe Firefox or Safari or Opera back in the day, but there was talk about how the operations were tied to the specific tab, not to the entire browser. So if I was working in one tab and some action I took in that tab overwhelmed it, only that tab was affected and the entire program did not have to be rebooted. It was revolutionary at that time back when!
I didn't know if that was an option in some way with VS. It may not be feasible but it was an idea I figured might help in some way as we think about ways to handle the times when we freeze up VS
