Inconsistent behavior of diagram query results created with Query Builder vs SQL

[PeterHeintz]

When defining queries of diagrams with the Query Builder, each row of the returned results shows the right diagram type icon and double click to a row opens the diagram.

When you do the same with SQL and using t_diagram.ea_guid as CLASSGUID and t_diagram.Diagram_type as CLASSTYPE the wrong icon is shown and double click does not work. Double click starts opening the right diagram after a “Find in Project Browser” is done row per row.

Further information:
http://www.sparxsystems.com/forums/smf/index.php/topic,39165.0.html

[qwerty]

You know that an official bug report need to be sent via the link down below in the support section?

q.

[PeterHeintz]

Yes, ticket is submitted. However in the ticket I point to this issue to make it public.

[qwerty]

Paolo just notes "reported" at the end. So everyone knows it's on rails.

q.

[qwerty]

Well, I found why you can't use t_diagram.diagram_type: It might return "Activity" and this will show the Activity icon. Anyhow, if there's no easy solution to show the diagram icon, it would be ok (I guess) to just show a common diagram icon with

Code: [Select]

"Diagram" as CLASSTYPE or the like.

q.

[PeterHeintz]

Thank you!
I will try something like this.

However my key feature I am looking to, is having the double click opening the diagram directly.
Basically I want to get rid of my huge amount of queries, by one, and adding the different diagram set types types in the <Search Term> like ‘Use Case’, ‘Test Case,..
I tried it with the Query Builder but I did not find a solution. Maybe you have an idea on having a type list in <Search Terms>.

[qwerty]

Except for using a smart add-in I'd have no idea. Paolo (IIRC) asked for more flexibility in the input of a search (like to have more than one input field). I guess a "real" smart solution is something you can't expect from down-under. Most times it's like "Oh, I have a nice hammer here. Let's see how we can use it for cooking."

q.

[PeterHeintz]

Yes, I remember to have voted for that Paolo issue.

In principle all what I need is there and there are several options that could do that, but each option has an other problem.

So just another “disregarded or off-limits flaw” (doof).

[Eve]

Well, I found why you can't use t_diagram.diagram_type: It might return "Activity" and this will show the Activity icon. Anyhow, if there's no easy solution to show the diagram icon, it would be ok (I guess) to just show a common diagram icon with

Code: [Select]

"Diagram" as CLASSTYPE or the like.

q.

Almost.

Use 't_diagram' as CLASSTABLE.

See the built in Recently Modified Diagrams search for an example.

[qwerty]

That was a quick one. I assume a mixed display of elements and diagrams would not be possible?

q.

[PeterHeintz]

Thank you Simon,
t_diagram' as CLASSTABLE makes all work.

I suggest that you also consider that magic thing in the user manual.

[Eve]

I thought it was, but the only reference to it in the current version of the manual is for connector types. (Which also share type names with t_object)