Add Element… doesn’t trigger sub menu (if the shape has one)

[Paolo F Cantoni]

If you drag an element from the toolbar and it has a sub-menu, the sub-menu will be displayed and you have to make the appropriate choice.

If you try to create the element via the Project Browser (via Add Element icon or Add Element... context menu item), the sub-menu is not triggered.

Concistency, konsistency, consistensy! ^TM_{Uffe - after Paolo}

Reported,
Paolo

[Paolo F Cantoni]

I've just been told by Sparx support, that this is the intended behaviour! 

Does any one agree that this inconsistency is GOOD?

To be clear, if I drag a BPMN::Activity off the tool bar, I get asked what kind it is.  If I do it off the browser, I don't.

Paolo

[Glassboy]

Does any one agree that this inconsistency is GOOD?

I'd answer but I fear I'd just sound like Gag Halfrunt.

[qwerty]

You mean "You know, Paolo is just this guy"?

q.

[Glassboy]

More like "EA just this application, you know".

[Paolo F Cantoni]

More like "EA just this application, you know".

Phew!  For a minute there, I thought I might be compared to Zaphod...

Maybe if a hyperspace bypass were to pass through...

Paolo

[Glassboy]

Phew!  For a minute there, I thought I might be compared to Zaphod...

Yeah, who would want to be considered interesting 

[Eve]

I'm glad you find the popup useful. I remember some negative feedback when we introduced it.

A decision was made that a popup menu doesn't fit in the UI for creating elements in this way. Given that a user can still change this after creation by setting the tagged value I wouldn't think it was a serious problem. Where would a popup be displayed?

Even if we found somewhere that worked to display the menu in this one place, others would have the same problem.

Create multiple elements from quicklinker
Apply the stereotype to existing elements (toolbox or dialog)
Package List, Specification Manager, Diagram List
Pattern import?
API

Even if it was possible to make all of these (except API) behave identically, I don't think it would necessarily make a better user experience.

[Paolo F Cantoni]

I'm glad you find the popup useful. I remember some negative feedback when we introduced it.

A decision was made that a popup menu doesn't fit in the UI for creating elements in this way. Given that a user can still change this after creation by setting the tagged value I wouldn't think it was a serious problem. Where would a popup be displayed?

Even if we found somewhere that worked to display the menu in this one place, others would have the same problem.

Create multiple elements from quicklinker
Apply the stereotype to existing elements (toolbox or dialog)
Package List, Specification Manager, Diagram List
Pattern import?
API

Even if it was possible to make all of these (except API) behave identically, I don't think it would necessarily make a better user experience.

(My emphasis)

Then you don't use EA in an enterprise scale production environment.

I may be creating 4-5 elements in a minute.  Holding the Add Element... dialog open means I can cut down the number of clicks and mouse movements to create elements.  Not being able to set  the sub menu means suddenly I have many more clicks and mouse movements per item and I have to post-process the items re-making decisions.

Carpal tunnel syndrome is a possibility.

Further as a casual end-user (that is MY users - whose day job is NOT modeller), it isn't apparent to me where the decision I've made ends up (that is did it set a tagged value and if so which one)?  We want to reduce "friction" for our end-users.  We're everywhere competing against Visio, other tools.

I've observed elsewhere that for a product named "Enterprise Architect", operating it at enterprise scale for enterprise models is problematic.

Now as to how far to make things consistent.

Sparx has already decided to make things inconsistent, "Madam, we've determined what you are, now we're just arguing the price."  I see no problem with gradually implementing the consistency over time.  Sparx might even ask the users what order they might like the mechanisms implemented. 

Paolo

[Eve]

Then you don't use EA in an enterprise scale production environment.

I may be creating 4-5 elements in a minute.  Holding the Add Element... dialog open means I can cut down the number of clicks and mouse movements to create elements.  Not being able to set  the sub menu means suddenly I have many more clicks and mouse movements per item and I have to post-process the items re-making decisions.

Carpal tunnel syndrome is a possibility.

Further as a casual end-user (that is MY users - whose day job is NOT modeller), it isn't apparent to me where the decision I've made ends up (that is did it set a tagged value and if so which one)?  We want to reduce "friction" for our end-users.  We're everywhere competing against Visio, other tools.

Funny, those are exactly the complaints we had from other users when we introduced that extra menu years ago. They don't want to do an extra click for decision they don't understand because they're used to Visio. Which illustrates that your requirements are not always the requirements of everyone else.

PS. Sure, when I'm really modelling I don't go at 4-5 elements a minute. I take more time on each element and make sure it's correct. When I'm creating a test model though I go much faster than that and with fewer clicks than using the Add Element Dialog. (Turn off edit element on new, drop one element, name it. Ctrl Click, name it, repeat. Creating elements using the quicklinker is almost as fast)

I don't agree that we've decided to make things inconsistent. We have tailored the user experience to what works in individual circumstances. It may just be a matter of terminology, but I know you're more than happy to quibble about that.

[Paolo F Cantoni]

My point was about just getting the objects into the repository and on the diagram.  Once they're in (and on the diagram), then we connect them up and do all the other stuff.

OK, maybe add the sub menu ONLY if the [X] Add Element to Current Diagram checkbox is marked,  I forgot, I almost always have it marked - hence why I mentioned dragging off the toolbar - so apologies for not being clearer before.  In both cases, then we end up with an element on the diagram - whether dragged or otherwise created.

If the checkbox isn't marked, it can be left as is.

Paolo

[skiwi]

We're everywhere competing against Visio, other tools.

Could not agree more.


_{"mostly harmless"}