Toad World® Forums

Code parameters tool tip shortcut doesn't work in Toad 11.0.0.116

Hi,

In Toad Options I have “Enable parameter assistance” turned on (and Use inline assistance turned off).

Whenever I write a procedure/package method/function name and then “(” I get the parameter list, but once it disappears pressing the Code parameters tool tip shortcut (CTRL+SHIFT+SPACE) doesn’t do anything.
The only way to get the parameters again is to delete the “(” and write it back again.
I also tried to change the shortcut combination under Editor–>Behavior–>Key mapping…–>Code parameters tool tip, but it did not change anything.

In version 10.6.1 it worked like a charm.
Please help!

Thanks.

This is a bug. The param assistance popup underwent some major changes for Toad
11 and the shortcut to show it was non-functional. I had it “fixed” prior to
release, but there were too many outstanding issues with it to keep it in place.
It’s on my TODO list for 11.1.

Michael

Thanks for acknowledging this as a bug.
I really don’t like the new param assistance - the old tooltip was just fine, but hey, that’s just me.

When is 11.1 going to be released?

btw, there’s also a very annoying bug of tabs stuck in “executing” even though the db session finished it’s work. Pressing “stop execution” or trying to close the connection do no good. It won’t even let close Toad normally. the only way out is to kill the process. Are you familiar with this bug? you can see other people complaining about it here: http://toadfororacle.com/thread.jspa?threadID=30082&tstart=0.

I really don’t like the new param assistance

Check out… View|Options|Editor|Code Assist. Uncheck “Use inline assistance”

When is 11.1 going to be released?

I believe in the spring. We just started the cycle.

tabs stuck in “executing” even though the db session finished it’s work.

What kind of statements are you executing when you see this behavior? If it’s
truly finished then we should get an end execution notification from the DB and
Toad should update accordingly. It sounds like we are not in your case. If you
have a reproducible case, run SQL Tracker (in same path as Toad.exe) and monitor
Toad. Reproduce your scenario and see if there is a query that is hanging. It’s
possible that your Toad options require some post-execution queries to be run
that may be problematic.

Pressing “stop execution” or trying to close the connection do no good.

In the past it has been brought up many times that query cancellation can be
slow. We send a cancel request and await the DB’s response. As far as I know the
delay is due to the DB or the client DLL taking a long time to process the
request, but my knowledge of the OCI and DB in this area is pretty shallow so
that’s just a guess.

Michael

“Check out… View|Options|Editor|Code Assist. Uncheck “Use inline assistance””
Quoting my original post:
In Toad Options I have “Enable parameter assistance” turned on (and Use inline assistance turned off). :slight_smile:

“I believe in the spring. We just started the cycle.”
Too bad. This was really a handy shortcut :frowning:

“What kind of statements are you executing when you see this behavior? If it’s
truly finished then we should get an end execution notification from the DB and
Toad should update accordingly. It sounds like we are not in your case. If you
have a reproducible case, run SQL Tracker (in same path as Toad.exe) and monitor
Toad. Reproduce your scenario and see if there is a query that is hanging. It’s
possible that your Toad options require some post-execution queries to be run
that may be problematic.”

I can’t reproduce really, since the statements that cause this vary. If I remember correctly it involved in some memory error or access violation error that toad popped up and then the tab got stuck. Other tabs in the same editor were still working, only the specific tab didn’t respond. I’ve encountered it about a dozen times already. This happened also in 10.6.1, so it’s not something that was introduced only in this new release.

“In the past it has been brought up many times that query cancellation can be
slow. We send a cancel request and await the DB’s response. As far as I know the
delay is due to the DB or the client DLL taking a long time to process the
request, but my knowledge of the OCI and DB in this area is pretty shallow so
that’s just a guess.”

I don’t think it’s actually trying to cancel the query execution or do anything related to the DB. My guess that it’s something more generic than that. If I remember correctly - the statements did finish on the DB side on all occasions- it’s not like I had a long running query that i’m trying to stop…

The next time it happens i’ll try to attach some screenshots.
-Mor

Quoting my original post: In Toad Options I have “Enable parameter assistance”
turned on (and Use inline assistance turned off). :slight_smile:

Sorry, I missed that. Besides the obvious bug regarding shortcut key activation,
what do you not like about it under those option settings? Are you noticing
differences in functionality? Using those options it should be functionally
equivalent to the old, if it is not then I may need to tweak some things.

it involved in some memory error or access violation error that toad popped up
and then the tab got stuck.

Now we get to the real problem. AVs and other unexpected exceptions will cause
unpredictable behavior. When you receive those errors please post here with your
Toad.elf file. In most cases that file contains the log data for unhandled
exceptions which helps us track down and resolve issues. Having a “force close
(or cancel)” option for a session or query execution is not really the solution
if the trigger is an AV that can be resolved. You will certainly encounter more
issues down the road even if Toad can allow you to forcibly kill a session or
close a tab.

The next time it happens i’ll try to attach some screenshots.

This won’t be necessary. The ELF file or a reproducible scenario are the two
things that will help the most. Feel free to send your ELF file to the list or
to me privately and I’ll take a peek. If you’ve experienced this issue in recent
weeks then the ELF file should contain valuable data.

Michael

Thanks for taking the time to answer and try to help.

I meant that I don’t like the new code assist. I like the good old tooltip much better, but it’s a matter of preference I guess.

Under these settings however I do have 1 thing that bothers me - when the pop-up appears the “End” keyboard button doesn’t respond (let’s say I have entered some parameters already and want to go to the end of the line to continue - I have to press CTRL±> until I get to the end of the line as a workaround).

Next time the “stuck tab” happens - I will send you the elf file (funny name :slight_smile: ).

Another btw - On rare occasions Toad just disappears - as if someone killed the process (but it wasn’t me). This also happened in both 10.6 and the new version. If it happens again i’ll send the elf file.

-Mor

Hi,

Yet another bug in the tooltip:
when inserting parameters, if one of them contains a ‘)’, like a call to a function or using “trunc(sysdate)” for example the tooltip disappears as if the ‘)’ marked the closure of the procedure call.

procedure foo has 5 parameters:
exec foo(param1, trunc(sysdate),…)
…^…^
here the tooltip appears | and here it disappears.

Hi,

It just happened again. I couldn’t find a way to message you privately, so I hope you read this:

The statement:
drop procedure procedure_name;

result - a pop up with the following error
:Access violation at address 004054EA in module ‘Toad.exe’. Read of address 0000003C

I ran this with SHIFT+F9 like I do 95% of the time.
note - the procedure was dropped.

there’s no ELF file in Toad’s directory, so there’s nothing I can send you really.

Please advise…
Thanks.

Check out…

View|Options|General and you’ll see a group box for Application Data Directory.
Navigate to that location. Toad.elf will be in there if one was generated.

michael.staszewskiquest.com

The tooltip should only close when the actual closing paren is entered. This is
fixed for next beta.