[4.0n & 4.1EA] control-clicking tablename or alias leads to "too many objects" warning

Actually it seems this is happening when the system has other objects by the same name,

and SqlDeveloper does not always open the correct one when Ctrl-clicking.

e.g. I reference table "TBL1" in a select, but when ctrl-clicking it from the worksheet,

it might be SOMEOTHERUSR.TBL1 that gets displayed (similar things may happen

with Shift-F4 but there I see no easy way of knowing the schema of the displayed object)

My limited testing suggests that Ctrl-clicking appears to end up displaying the details of the object

that lives in the schema that comes first alphabetically - picking the object from the connexion's

schema (if one exists) would seem like a better default...

I am on win7 32bits, sqldeveloper  Version 4.0.2.15

to avoid posting actual object names, I'll keep the description close to what I already explained:

Select *
from TBL1
order by created_at desc;

I am connected as user 'Zxyz', the query above returns content from the table TBL1 in the current schema (as it should, the db sql engine picks the correct table), but ctrl-clicking "TBL1" opens Axyz.TBL1, as user Axyz also has a table by the same name, on which I have grants.

If I prefix TBL1 with its owner, the correct one is displayed, but it is cumbersome to have to do that for all table references, and one can easily get confused by the current behaviour where sqldeveloper actually shows the details of a table which may not be the one effectively used at runtime.

Note that there are several schemas with identically-named tables (more than 2), hence I suppose the original symptom mentioned in the subject, but some more investigation led me to notice the wrong object sometimes gets displayed