Project

General

Profile

Change Request #2740

Port setting propagation should not change target/source port names

Added by Anonymous almost 4 years ago. Updated 7 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
Start date:
11/21/2016
Due date:
% Done:

0%

Estimated time:

Description

Currently, this breaks code specifications and creates wrong unsuitable port names

History

#1 Updated by Anonymous almost 4 years ago

Mmmh, I understand the problem but not with the solution: changing the name is precisely the purpose of propagation.

Maybe we could make an additional dialog, which pops up and asks "Do you want to also change the name of the ports inside the code specification/automaton/etc.?".

#2 Updated by Anonymous almost 4 years ago

  • Assignee changed from Anonymous to Anonymous

(assigning to you cause I'm not sure you get a notification when I write a comment)

#3 Updated by Anonymous almost 4 years ago

I would avoid bringing up additional modal dialogues at any cost.

It is a matter of point of view.

- If a model is viewed as "system composed of components", then you are right as it is about a specific information fragment being processed in the system.
- If a model is seen as "components hooked together to form a system", then it is more about components and their interfaces. Here, propagating a port name is suboptimal.

So I can just provide an opinion/suggestion. There might not be a perfect solution.

#4 Updated by Anonymous over 3 years ago

  • Target version changed from AF3 2.11 Release to AF3 2.11 Post-release

#5 Updated by Anonymous over 2 years ago

  • Target version changed from AF3 2.11 Post-release to AF3 2.14 RC2 (Tested, Bug-free)

#6 Updated by Johannes Eder over 1 year ago

  • Assignee set to Anonymous
  • Target version changed from AF3 2.14 RC2 (Tested, Bug-free) to Backlog

#7 Updated by Johannes Eder 7 months ago

  • Status changed from New to Rejected
  • Assignee deleted (Anonymous)

Also available in: Atom PDF