Book a Demo

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - elr

Pages: 1 [2] 3 4
16
OK, It requires an add-in setup. It's another step for me.
but I'll throw a look into Geert's work.

Thx for all, qwerty !

Eric

17
Quote
The attributes are only available via the classifier (which you have ro set manually)

Too bad...

And what about a code sequence being fired when TB element is dropped to diagram ? Is that possible ?


Eric

18
Yes,qwerty I configured it that way (as an object stereotype in my TB as Eve recently recommended me), but then...how can I access attributes of the metaclass and, even better, values of theses attributes that have been defined so far?

For example:
  for:   Committee.name='Steering committee'
 
  being able to get:  Committee instance.name =:Steering committee
by selecting in a listbox among all existing names

  instead of simply getting :  :Committee Instance

In metamodel, what should be the relation type between  Committee stereotype that extend Actor metaclass and Committee Instance stereotype that extend Object metaclass  to make Committee element attributes, TV accessible to Committee Instance element ?

 :-\

Eric

19
Quote
to drop the classifier on the diagram...

Do you mean : Dropping a class onto diagram then selecting the element it's an instance of through Advanced/Instance Classifier ?

Eric


20
Hi Geert and (once again...) thx !

"Yes, I have added to  my toolbox an element named 'committee instance', which is a stereotype of Object metaclass. This metaclass is connected (I logically used an 'instantiates' relationship) to the Committee stereotype of the Actor metaclass."

This approach seems to work. But then, I don't know how to retrieve the list of already defined committee names in order to specify which committee this newly created instance is of. 

Hope to be clear...  :-\ ( I don't know how to show my metamodel fragment...


Eric

21
Hello all,

I created an MDG profile with several stereotyped elements.

One is 'Committee' : a stereotype of Actor metaclass with a dedicated shape (set with ShapeScript)
Once one is created in Browser, I can drag it drop as an Instance (Ctrl-DnD) in my diagram but then, visual aspect becomes again the Actor's stickman and not the shape I set up
 :(
Ideally, I'd like to do as UML Profile: same shape with a different color and a underlined name.

Thank's for your recipe !


Eric

22
Thank you Eve !
and no problem, qwerty.  I suspected the mix-up, but the thread I referred, made it as well..
:)

Eric

23
Hi qwerty,

In my case, D'nD and Ctrl+D'nD from Toolbox do exactly the same :(  It places an exemplary  (instance ?) of the element I chose, with an incremented serial number.

https://sparxsystems.com/forums/smf/index.php?topic=37874.0

Maybe my answer could come from recovering this feature...
 ???

Eric




24
Hello and thank you two,

I experimented _instanceType property by setting its value to _metatype value defined for my stereotype  (I hope to be clear...). Drag'n Drop an element from the browser window let me opt an instance of my stereotyped class. But then:
1. I don't catch the difference (aspect and behavior) with creating many times stereotyped elements :

EventType1.Date=date1, EventType2.Date=date2, EventType3.Date=date3...
vs
date1:EventType1, date2:EventType1, date3.EventType1...
(not sure I'm still clear :-[ )

2. There is no visual difference unlike Standard UML profile that underlines name and sets to blue each instance's background.

What I was first expecting was to drag'n drop my stereotyped element directly from a Toolbox (maybe in a  specifically configured diagram's stereotype)  to instantly get a recolored instance of it, pre-fixed with <instance_name> and post-fixed with:<Element_name>

...Thx for reading  :)

Eric


25
Automation Interface, Add-Ins and Tools / Re: Starter MDG Example
« on: September 20, 2024, 05:02:59 am »
Hi Tim,

Have a look at Phil Chutley's videos for past EA Global Summits

https://www.youtube.com/watch?v=385d7bv7GUE
https://www.youtube.com/watch?v=UgKTAIymgeo

That greatly helped me to start with MDG.

HTH

Eric

26
Thank you two !

@Geert: Ctrl+Drag seems clean but I actually I get metaclass icon instead of stereotype one :(
@qwerty : I suppose that's a diagram property... I'll check it out but I'm afraid I'll then get the same glitch (default object icon)

So my work is not over if I want to get both class and object



27
Hi Geert  and one more time thank you for you time !

Quote
You should probably create another stereotype for an eventType instance
Does it means that my toolbox would propose EventTime and EventTimeInstance icons ?

Quote
On the EventType stereotype you can indicate which stereotype is to be used for instances.

Unfortunately, I don't master more than that P.Chudley shows in its Getting the best out of an MDG video
:(

Finally solution seems not linked to diagram's types or properties. But, when you drag a class onto a diagram,what makes it show or not a window to choose between a  link or instance ?

Eric

28
Hello all,

I'm setting a customized MDG techno for office management with classes based stereotypes.  For example, I created an Event element embedding a EventType Tagged Value (Meeting, Interview, Appointment, Seminary and so on)

As it works fine when I drag it from my Toolbox to an empty stereotyped diag (thx Phil Chudley) I wonder if that would be possible to  instanciate this Event stereotype not as classe but as an object (maybe onto another stereotyped object diagram ?) that would easily represent each occurence of event.

I feel that setting the TV would be an issue....
Will I need to step back and build each event type as a stereotype


Thank you for your help

Eric

 

29
General Board / Re: Types of classes attributes
« on: September 07, 2024, 08:34:46 am »
Impressed by AI's kind of knowledge...
I'll think about it, in the future

Thank's Geert.

30
General Board / Re: inherited tagged values in a profile
« on: July 30, 2024, 10:40:03 am »
I see. No need for inheritance, thus..
Thank you !

Eric

Pages: 1 [2] 3 4