Identifying diagrams with same names

[jamessher]

Hi,

I have lots of diagrams in quite a large project which have the same name, eg. Use Cases. When several are open the names on the tabs are obviously all 'Use Cases' so there is no easy way to know which one is which. I can of course name then better eg. 'Foo Use Cases' and 'Bar Use Cases' but this shouldn't be necessary since they are already 'name scoped' by the packages in which they are contained.

Even when I select the diagram there is nothing in the diagram title (eg. 'Use Case Diagram: "Use Cases" created...) which helps identify where it comes from in the Project Browser/Model. Obviously again I can add additional info in the diagram itself which helps to identify its location in the model, but I would have hoped this shouldn't be necessary.

I can't even right click on the diagram and do the equivalent of 'Find in Project Browser', which is a nuisance.

Does anyone know if there is someway to make diagrams with same names more easily identifiable as to where they come from in the model (location in Project Browser) without having to resort to long-winded diagram names ?

Sorry for being demanding here - I just find it frustrating to have to build the 'name scope' into the diagram names when it is already available in the model. It also makes the model difficult to maintain because the 'name scope' appears in lots of diagrams and if I move the diagram to a different package location the names of the diagrams may need to be all changed.

Hopefully there is some way to deal with this without it becoming a feature request  

Thanks
    James

[Oliver F.]

The interesting thing would be to analyse what makes those diagrams unique...

To find the diagrams again one would have to define a unique criteria anyway, otherwise it will result in a hard time when searching.

Eg. is there a central UC in each diagram which does not appear elsewhere, different phases, versions, etc.
That could be a basis for a search view.

7.1 has a very interesting new feature about views which can be bound to search criteria.

I hope this helps at least a bit.

Oliver