In your post from 6:19 you asked: “How is it behaving differently?”
I think your post at 6:23 answers the question: “the only visual indicators you’ll see are the throbber at the bottom right, Toad can’t be closed, etc.”
If Toad cannot be closed, and if Ctrl_Enter does not start a query but inserts a new-line character instead, then somehow Toad behaviour is being influenced by the fact that the query has nor properly been cancelled.
I do not know how these circumstances affect Toad behaviour in the extent that they (observably) do, but it does happen. One would think that somehow, this information must be available to Toad: “cancellation of thread still in progress”.
building on the conclusion above that Toad must somehow be aware of the still-pending status of the cancellation request, would it then be possible to issue a stronger command to Oracle to cancel the thread immediately?
Or, alternatively, to disconnect from the thread on the Toad side, so that Toad behaviour reverts to normal? Brining up a pop-up to allow me (the user) to choose how to deal with the strong-headed thread refusing to be cancelled would be quite ok, of course.
Returning to the basic why: I love it that I can continue to edit while the query executes. I have no problems with the need to cancel a running query, in case I want to run a modify version.
But I detest of having to use windows to force-close Toad in order to be able to issue a new query when Oracle refuses to cancel a thread.
It is cumbersome, time-consuming and tedious because - apart from closing and restarting Toad - I have to save and re-establish all work in progress.
I’m on the ouside looking in, and from my vantage point it looks like it should be doable.
However, you’re on the inside and should be able to determine whether or not my conjecture is correct.
If it’s not doable, then so be it.