Book a Demo

Author Topic: Call behavior action pins do show parameter names but not parameter types of cal  (Read 7917 times)

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
In the current released build 1554, call behavior actions pin still do not show the classifiers of the related parameters.
Best regards,

Peter Heintz

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
Still not working in build 1555. Will there come a day when it works again?
Best regards,

Peter Heintz

Eve

  • EA Administrator
  • EA Guru
  • *****
  • Posts: 8110
  • Karma: +119/-20
    • View Profile
Have you reported it? There's not enough information here to reproduce your problem. I just created a new CallBehaviorAction and the Pin type1 is copied from the parameter and displayed.

1 It doesn't actually have a classifier.

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
Hi!
My number for this enquiry is : 20095589.
The problem was already in some early V14 versions but fixed (as I remember).
In V15 the problem came again.

In Build 1555 I see a small improvement. Apart of some refresh problems is see pin types in compliance to parameter types on the diagram and within the element properties again but not in the interaction points of the action.
Further on if I change to parameter type the pin types get not updated.
 
Best regards,

Peter Heintz

PeterHeintz

  • EA Practitioner
  • ***
  • Posts: 1001
  • Karma: +59/-18
    • View Profile
In build 1557 something happened regarding that issue. Now it seems, as long as a classified parameter has got a name as well, it works.
If a classified parameter has got no name, the classifier is not taken over in the calling action pin.
If a classified parameters name is removed, the pin continues to be classified according to the parameter but the pin classifier is not shown in the diagram any more.

Further on, somehow I managed to come very quickly in an endless “Unsaved Parameter Changes” dialog loop.
Best regards,

Peter Heintz