This has been implemented for Toad 12.5.
when I press a fullstop after a tablename toad can take forever to try and offer a list of columns. If we have network /database issues on that day this can take ages until it times out. Pressing escape key to cancel this would be great.
Escape does close the popup window. However only after it pops up. It'd be nice if you could hit Escape during the (configurable) delay period and not even have it pop up in the first place. I get a lot of code completions I don't even want, and it's become annoying. Also, I get a lot of GPF's that crash TOAD during the code completion popup because of the large number of elements. Some smarter emmory allocation is probably in order to limit the number of items in the popup.
For me it is reasonably fast.
I suspect that your second threaded connection the editor uses hangs. It may happen if not used for a certain time (usually due to firewalls).
If your threaded connection is hung, try disabling
Execute queries in threads
in View, Toad Options, Oracle, Transactions
Eventually may help increasing
in Editor, Code Assist
So it waits for more time before completing.
A space after the dot does not complete.
for avoiding the second session (Toad 11), shown as
"TOAD background query session"
Toad Options -> Editor -> Display
and disable all Syntax Highlighting ticks
otherwise this session times out.
Code completion is ridiculous when you are connected to a database on the opposite side of the world with bandwidth on the order of kb/sec.
This has been implemented for Toad 12.5. It will be available in the next beta which will be version 18.104.22.168. If you are a beta participant I encourage you to try it out and provide feedback.
Pressing ESC will cancel Code Insight while it it is loading and close it if it's already loaded and displaying results. The population of Code Insight requires execution of multiple queries as well as parsing of the Editor text. All query execution is now threaded. Results display in the popup as they are available; however, the popup cannot be used until it has fully loaded so you'll notice that it populates incrementally. On fast access DBs this effect is barely noticeable, but on slower connections or on those DBs where there are many objects returned you'll see it. Load time of the popup will likely be slightly increased over previous versions because threaded execution typically takes longer to complete and a background connection to your DB must be established, but it prevents Toad from locking up and allows for cancellation.