Project

General

Profile

Feature #2890

Parameters shall be usable in expressions

Added by Anonymous over 3 years ago. Updated over 1 year ago.

Status:
In Progress
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
03/21/2017
Due date:
% Done:

70%

Estimated time:

Description

Requirements now allow to define "Parameters". Would be nice if these parameters could be usable in the model itself.

History

#1 Updated by Anonymous over 3 years ago

  • % Done changed from 0 to 70

parameters can now be used in the component architecture. they need however to be provided with a type so that this use is correct. Error message could be improved actually in case of missing type...

To use the parameter also in simulations, one also need to provide a value (which is not necessary if you just want to model symbolically). At the moment the error message in case of missing value is also not nice.

Only remaining task is to adapt code generation.

#2 Updated by Anonymous over 3 years ago

also code completion in state automaton guards/actions

#3 Updated by Anonymous almost 3 years ago

  • Target version changed from AF3 2.12 RC1 (Feature Freeze) to AF3 2.13 RC1 (Feature Freeze)

#4 Updated by Anonymous over 2 years ago

  • Status changed from New to In Progress
  • Assignee changed from Anonymous to Andreas Bayha

@Andreas: like for the other issue, this is about reuse. More precisely about projects with parameters.
We can now use the parameters in a model, but cannot do code generation. I think it's the only missing thing. Now a question would be if it really makes sense to have code generation for projects with parameters but I do think so. Parameters could be defined via preprocessor constants.

#5 Updated by Johannes Eder over 1 year ago

  • Target version changed from AF3 2.13 RC1 (Feature Freeze) to Backlog

Also available in: Atom PDF