Add choose to "type" drop-dowlist of a requirement

[Monsieur]

Requirements show the stereotype in the Type field. It also behaves a bit different. EAUI that is....

q.

Dear Q,
Can you show me your UI so i can see the difference?
In advance, thank you.

I'll ask if IT department can install EA from scratch on a corpo VM and a free corpo VM and see if the problem dosn't come from upgrading EA instead of uninstall/install and see if the corpo environment is responsible for that weird UI.

[qwerty]

You see the stereotypes as being set in the internal table for a requirement and a class. The requirement's stereotype is shown in the Type field. Further EA lets you select the preset values (Functional, etc.). So this is a typical example of EAUI.

q.

[Monsieur]

You see the stereotypes as being set in the internal table for a requirement and a class. The requirement's stereotype is shown in the Type field. Further EA lets you select the preset values (Functional, etc.). So this is a typical example of EAUI.

q.

Yeah but shoulsn't it be a (...) button?
I don't get what i should or shouldn't have that's why a screenshot is welcome.

Plus the help says you can check multiple stereotypes??
http://www.sparxsystems.com/enterprise_architect_user_guide/10/standard_uml_models/stereotype_picker.html
How to get that feature??
I only got a dropdown list, not a list with checkboxes!

[qwerty]

As I said: EAUI (EA Unique Interface). Send a feature request if you like. Or poke your finger in your nose if that's more pleasant  

q.

[Monsieur]

As I said: EAUI (EA Unique Interface). Send a feature request if you like. Or poke your finger in your nose if that's more pleasant  

q.

Sorry, i wasn't familiar with EAUI (i thought it was for User Interface and not Unique!).

I am a bit lost:

-So you say that my interface is not the "normal" interface of enterprise architect???

-Where do i send a feature request? Are you talking about the "Suggestions and Requests" part of the Forum?

All i want is to get back to a classic interface and the New button, the (...) button and all these awsome features!  

[qwerty]

Well, this unnormal appearance is what EA shows everyone. This likely has historic roots and never has been normalized. I refer to the "Feature Request" link bottom right of this page. Don't put much hope in using this. We're seeing these Requirements properties since more than 12 years.

What you could do is to create a Requirement based on the meta-class Class instead of Requirement.

q.

[Monsieur]

Well, this unnormal appearance is what EA shows everyone. This likely has historic roots and never has been normalized. I refer to the "Feature Request" link bottom right of this page. Don't put much hope in using this. We're seeing these Requirements properties since more than 12 years.

What you could do is to create a Requirement based on the meta-class Class instead of Requirement.

q.

If i understood right, every one has this requirement interface (with no button (...) etc) and that should be corrected (if sparx decide to do it someday...)

Q, as always, you are right.
The Class interface is more "normal".
I maybe try to make my requirement based on the Class metaclass IF i can find a way to hide some of the properties (Like template, Advances or Rules!) and get to an "alike" interface of a requirement.


Thank you for giving some of your time to the community (well, to me in that case   )

[qwerty]

Unfortunately the properties window(s) can not be modified, though it has been asked quite many times. You "could" write your own properties dialogue. But that's definitely not trivial and likely overkill. You could however  react on changes in properties with an add-in listening to OnContextMenuChanged (or how it's called).

q.

[Eve]

Version 12 is now using the same properties dialog for Requirements and other elements.

[qwerty]

That sounds like a good change once in a time  

q.

[Monsieur]

Hello all,

Still discovering the stereotype selector and i have a few questions:

When you click on the "..." button, a frame open and allow you to select the stereotype BUT you can check multiple boxes HOWEVER once you click ok you only have one stereotype.

Why is there checkboxes and can we make multiple choice if in the end it all end with the first choice of your list (in the weird order of EA).
  :-? :-?

[Geert Bellekens]

If you choose multiple they are actually all selected, but you only see one in the properties dialog.
Check the same element on a diagram and you will see the different stereotypes.

Geert

[qwerty]

As a (EAUI) side note: enter some stereotypes separated by comma (and no space!)  in the stereotype field. Now when you open the ...-dialog you see that each of them is checked.

q.

[Monsieur]

If you choose multiple they are actually all selected, but you only see one in the properties dialog.
Check the same element on a diagram and you will see the different stereotypes.

Geert

I'm just blind, thank you for the info Geert, it perfectly works.

As a (EAUI) side note: enter some stereotypes separated by comma (and no space!)  in the stereotype field. Now when you open the ...-dialog you see that each of them is checked.

q.

Yes, I saw that, but that method is a bit messy, I don't want some one "killing" the model with a mistake (likely a miss-spell or a "s" or whatever)

Just a new question, when I click the "..." button, I don't see my customised profile from my MDG, is that normal? (I got access to those stereotype from the toolbox I made although)

[qwerty]

Just a new question, when I click the "..." button, I don't see my customised profile from my MDG, is that normal? (I got access to those stereotype from the toolbox I made although)

Strange, normally I see my profile in the list. Is your profile enabled in the settings?

But to add injury to insult: The Profile field is a combo-box?!?!   I never noticed that before (using V11). Why should one be able to type free text in the profile name?

q.