Highlighting plugin VS. hyperlink navigation

[zoftland]

Hi!

When I use the Highlighting plugin with the SELECT below then the hyperlink navigation doesn't work properly (Can't jump to the selected procedure).

select object_name
from all_procedures a
where a.owner = User
union
select procedure_name
from all_procedures a
where a.owner = User

 

[Marco Kalter]

You probably need to assign the "custom" style to these keywords. Other styles may cause the hyperlink navigation to skip the keywords.

 

[zoftland]

I exactly used the "custom" style! But it doesn't count what I've adjusted!

 

[Marco Kalter]

I'm not sure what you mean. Can you clarify? Note that I am talking about the Custom style from Style selection list on the General tab page of the Highlighting Configuration screen.

 

[zoftland]

No! Sorry, I've been talking about the Syntax Highlighting PLUG-IN !!! It's yours tool too, isn't it?

 

[Marco Kalter]

That's what I'm talking about as well. Go to Tools > Syntax Highlighting, and select Custom from the Style selection list on the General tab page. This menu item and this configuration screen is from the Plug-In.

 

[zoftland]

So we're talking about the same thing. But if you write the above select into the plugin box, then every package, their functions and procedures will use the custom color settings. It's wonderfull!

BUT then, you can't use the CTRL+right button pointing a procedure of package!!!!
(6.0.1 Developer)

 

[Marco Kalter]

Well, if I try this it works just fine. I used your query, all program units now have a custom color, AND I can Ctrl-Click on them for hyperlink navigation. I'm using 6.0.1 as well.

 

[zoftland]

The underlined selection appears the name of the package OR the procedure BUT not for the utter calling. So I can open the called package, just the cursor doesn't jump to the selected proc (in the spec or body).

So, if your cursor jump to the correct place, I must have spoilt something!?
I should have explained the problem exactly sooner.

 

[Marco Kalter]

AH, I see what you mean now!

We'll fix it for 6.0.2.