Author Topic: Create Accept Timer Event in toolbox  (Read 2879 times)

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Create Accept Timer Event in toolbox
« on: December 13, 2019, 04:12:38 am »
So, what is the metatype to extend here? I tried AcceptEventTimerAction which I found in the SysML from EA's guts. That "sort of" worked, but the icon in the toolbox just shows the guillemets (for a wrong definition, which btw. also appears when using UMLPatternSilent). Also I can't seem to get  stereotyped version of that (I want my own stereotyped timer event). The previously mention one creates a bare timer element.

I'm working on 13.5 and no way to upgrade.

q.

KP

  • EA Administrator
  • EA Expert
  • *****
  • Posts: 2919
  • Karma: +54/-3
    • View Profile
Re: Create Accept Timer Event in toolbox
« Reply #1 on: December 13, 2019, 08:57:01 am »
If you just want to add an unstereotyped one to a toolbox, use "UML::AcceptEventTimerAction".

But if you want to extend one with a stereotype, create a stereotype that extends Action, and in the metaclass set the value of the "kind" attribute to "AcceptEventTimer".

The Sparx Team
[email protected]

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Create Accept Timer Event in toolbox
« Reply #2 on: December 13, 2019, 11:21:28 am »
Thanks. I'll try that (after I've slept :-)

q.

qwerty

  • EA Guru
  • *****
  • Posts: 13584
  • Karma: +396/-301
  • I'm no guru at all
    • View Profile
Re: Create Accept Timer Event in toolbox
« Reply #3 on: December 13, 2019, 09:15:14 pm »
Hi KP,
It seems that both ways create the same result. (I found the  "UML::AcceptEventTimerAction"-way right before.) But when you look into the database you find that a basic timer event (which can only be created from the context menu?) has NType = 2. The ones I created with my MDG do not have NType = 2 but 0 like a normal send (receive has 1 in that place). I'll probably can ignore that fact since (I guess) that's just evaluated for rendering an element and my shape script overrides the rendering. Right?

q.