Toad World® Forums

Ctrl-T not working

All,

I’m on Toad 12.10.0.25.

While changing a package I’m rewriting a call to a package in another schema. After the schema_name and the period, I hit Ctrl-T to get a pop-up of valid names in the schema.
Nothing happens. Neither a pop-up nor an error message appears.

I double-checked the schema_name: it has been spelled correctly.

Also, there are no syntax errors in my package, other than the incomlpete statement I’m trying to modify.

Is this a known issue?
I’ve encountered similar situations in the past.
After filling the corerct package name, the issue repeats: no pop-up available, apparently.
With F4 I can work around it, but it’s less convenient than Ctrl-T.

After typing the opening parenthesis to start the argument list, no prototype parmlist is inserted either.
Again, with F4 this can be overcome, but it’s less practical.

I’m attaching the source code for what it;s worth,. The problem statement is on line 241.

[View:/cfs-file/__key/communityserver-discussions-components-files/86/send_5F00_receive_5F00_msg.txt:320:240]

Do you think this can be mended or am I doing something wrong?

Kind regards,
Abe Kornelis

Abe I cannot reproduce, but I’m not certain if I’m doing the steps correctly.

I have a sample package that is being called…

    CREATE OR REPLACE PACKAGE test_called_pkg
AS
pkg_var VARCHAR2 (100);
pkg_const CONSTANT VARCHAR2 (100) := 'Hello World';
PROCEDURE proc_1 (p1 IN NUMBER);
PROCEDURE proc_2 (p1 IN NUMBER, p2 OUT DATE);
END;
CREATE OR REPLACE PACKAGE BODY test_called_pkg
AS
PROCEDURE proc_1 (p1 IN NUMBER)
AS
BEGIN
NULL;
END;
PROCEDURE proc_2 (p1 IN NUMBER, p2 OUT DATE)
AS
BEGIN
p2 := SYSDATE;
END;
END;

…and a sample package referencing the called package…

    CREATE OR REPLACE PACKAGE test_call_pkg
AS
PROCEDURE proc_1;
END;
CREATE OR REPLACE PACKAGE BODY test_call_pkg
AS
PROCEDURE proc_1
AS
BEGIN
MSTASZEW.TEST_CALLED_PKG.PROC_2( -- Editing line
END;
END;

On the line I’m editing I invoke Code Insight and select the test_called_pkg and then a procedure name. I type an open parenthesis and the parameter signature is inserted. I then delete all text up to the schema name and add a period and manually invoke Code Insight with CTRL+T and repeat the process selecting test_called_pkg, a procedure name, and open parenthesis and wait for the parameter signature. It’s all working as expected in my simple test.

Is this what you’re doing? If you have the option enabled to cache Code Insight data on the Editor|Code Assist page in Options you can disable that and see if it corrects it. The cache option can prevent Code Insight from showing changes until the list is manually refreshed (refresh button in Code Insight popup). However, it should still show the popup, but with stale data so this may not be the cause.