SpaceCreator issueshttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues2024-03-20T08:47:54Zhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/1126IVE: Function moves, when opening the properties dialog2024-03-20T08:47:54ZGuenter SchwannIVE: Function moves, when opening the properties dialogHerre you can see the function (and therefore interfaces and connections) movint when opening the dialog:
![mess](/uploads/5b58c502812d224050cfc37bbaaefae2/mess.gif)
It happens only after loading the model.
on the first property ope...Herre you can see the function (and therefore interfaces and connections) movint when opening the dialog:
![mess](/uploads/5b58c502812d224050cfc37bbaaefae2/mess.gif)
It happens only after loading the model.
on the first property opening dialog. afterwards if you replace things, it does not happen anymore
[interfaceview.ui.xml](/uploads/0a0dbb2fdca9b7e159cfdbaffb5e1665/interfaceview.ui.xml)
[interfaceview.xml](/uploads/5a1ba64ead7d871822d6c3e5ccdc2dd6/interfaceview.xml)5 Bug fixeshttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/1064Add review tab to IV/DV properties dialog2024-03-20T07:55:32ZGuenter SchwannAdd review tab to IV/DV properties dialogAdd a tab in the component properties for IV and DVAdd a tab in the component properties for IV and DV2 Review of a modelHugo Jiménez HernándezHugo Jiménez Hernándezhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/1040IVE: Function instantiated from Shared Library doesn't reflect changes2024-03-20T10:22:48ZAlex DievIVE: Function instantiated from Shared Library doesn't reflect changesFunction instantiated from Shared Library doesn't reflect changes done with the Type after saving instance in the model. Even after model reloading.Function instantiated from Shared Library doesn't reflect changes done with the Type after saving instance in the model. Even after model reloading.Guenter SchwannGuenter Schwannhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/993IVE: Multiple connections for the same interface can merge2024-03-20T08:48:21ZGuenter SchwannIVE: Multiple connections for the same interface can mergeWhen multiple connection end at the same interface, their paths should be merged if possible.
This wold create a cleaner layout.
![image](/uploads/88b61b8302855ec81c5e50b073219534/image.png)
![image](/uploads/d9db6ead6609897512de68...When multiple connection end at the same interface, their paths should be merged if possible.
This wold create a cleaner layout.
![image](/uploads/88b61b8302855ec81c5e50b073219534/image.png)
![image](/uploads/d9db6ead6609897512de68f328dad9b6/image.png ![moving_issues](/uploads/2bfb6a9e8850c3ed6676ccc6e10b7e1c/moving_issues.gif)5 Bug fixesDenis GofmanDenis Gofmanhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/990IVE: Update instances, when the model in the library changes2024-03-20T10:22:53ZGuenter SchwannIVE: Update instances, when the model in the library changesSteps to reproduce:
* Have a interface view mode with a function that is an instance of a component in the shared library
* Edit the shared component (add/remove interfaces)
-> the instance shall be updated to reflect the changes
- [ ]...Steps to reproduce:
* Have a interface view mode with a function that is an instance of a component in the shared library
* Edit the shared component (add/remove interfaces)
-> the instance shall be updated to reflect the changes
- [ ] If an interface is removed from the component type: it must be removed from all instances (in the current open model). This will make the connections disappear.
- [ ] If an interface is just renamed in the component type: it must be renamed from all instances, but connections remain
- [ ] If an interface parameters have changed then the changes have to be applied on instances and connected functions. That will break user code of the callees and the model will most likely not compile anymore but it is the user responsibility to apply the change.Guenter SchwannGuenter Schwannhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/986IVE: Check backlog for further issues2024-03-20T08:56:35ZGuenter SchwannIVE: Check backlog for further issuesCheck https://gitrepos.estec.esa.int/taste/spacecreator/-/wikis/Backlog what items to implement.Check https://gitrepos.estec.esa.int/taste/spacecreator/-/wikis/Backlog what items to implement.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/983IVE: Nested functions inside nested functions don't work well2024-03-20T10:14:34ZGuenter SchwannIVE: Nested functions inside nested functions don't work wellNested functions inside nested functions don't work well.
![image](/uploads/00dd0be4fb6818c3a7ec3a9d302ce065/image.png)
they open like this:
![image](/uploads/c047a911588b4a389d89421c743c4f2f/image.png)
Just create a nested funct...Nested functions inside nested functions don't work well.
![image](/uploads/00dd0be4fb6818c3a7ec3a9d302ce065/image.png)
they open like this:
![image](/uploads/c047a911588b4a389d89421c743c4f2f/image.png)
Just create a nested function and then another nested function inside, then you'll get to the 2nd screenshot. Try to resize things and all weird behaviours happen.
Also including some unexpected renamings of RIs
![image](/uploads/868ed105a43e77197627b390754a14f2/image.png)
Basically at the 2nd level of nesting, the function gets a tiny size:
![image](/uploads/4066eb74d5320c7f3491cb3e2fc8c11a/image.png)Guenter SchwannGuenter Schwannhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/978IVE: Support attribute regular expression per scope2023-05-15T08:34:27ZGuenter SchwannIVE: Support attribute regular expression per scopeTo avoid having a hardcoded exception in `IVAttributeDelegate` for connection groups, add support for regular expressions for attributes per scope.
As connection groups can have spaces etc. in their name.To avoid having a hardcoded exception in `IVAttributeDelegate` for connection groups, add support for regular expressions for attributes per scope.
As connection groups can have spaces etc. in their name.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/966IVE: One componoent not loaded to library2023-05-12T07:38:30ZGuenter SchwannIVE: One componoent not loaded to libraryOne of the three components in the attached library is not loaded.
[comp1.tar.bz2](/uploads/c3726e0e8cbe00bcbde2d7121bfe0dd1/comp1.tar.bz2)One of the three components in the attached library is not loaded.
[comp1.tar.bz2](/uploads/c3726e0e8cbe00bcbde2d7121bfe0dd1/comp1.tar.bz2)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/963IVE: Connection group style not applied initially2023-04-26T10:06:56ZGuenter SchwannIVE: Connection group style not applied initiallyThere is a tiny bug when loading a model that contains a connection group, while the connection group style has been modified.
When I open the model the connection group appears without any style:
![image](/uploads/caafe9d48978c803e553...There is a tiny bug when loading a model that contains a connection group, while the connection group style has been modified.
When I open the model the connection group appears without any style:
![image](/uploads/caafe9d48978c803e553bd27fc387e8b/image.png)
If I then click on the connection group, the style is applied:
![image](/uploads/1e92b049fc74aa5b075b3f71e2969872/image.png)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/908IVE: Supported version check in the XML parser2023-05-12T07:39:16ZAlex DievIVE: Supported version check in the XML parserAdd an ability to check if version is supported for proper XML data parsingAdd an ability to check if version is supported for proper XML data parsinghttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/881IVE: New scope for attributes file2024-03-20T08:50:27ZGuenter SchwannIVE: New scope for attributes fileAdd new scope for "is_instance" in the attributes file. For functions that are of type "is instance".Add new scope for "is_instance" in the attributes file. For functions that are of type "is instance".https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/842IVE: Compare ASN.1 files by objects during import2023-04-11T08:19:47ZAlex DievIVE: Compare ASN.1 files by objects during importCompare ASN.1 files by model objects during import instead of just simple text file content comparisonCompare ASN.1 files by model objects during import instead of just simple text file content comparisonhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/798Interface attributes on function types get not inherited by their instances2024-03-20T10:13:38ZMassimo NazariaInterface attributes on function types get not inherited by their instancesHi all,
We are having this issue about interface attributes on instance functions (i.e. Functions that are instances of Function Types).
In our case I explain below, the instance Functions do not inherit all the interface attributes we...Hi all,
We are having this issue about interface attributes on instance functions (i.e. Functions that are instances of Function Types).
In our case I explain below, the instance Functions do not inherit all the interface attributes we set on the corresponding Function Types.
In particular, we added two boolean attributes on PI/RI interfaces of kind Unprotected to be set on the interfaces via Right-Click -> Properties:
* is_alarm, and
* is_observable (we added these attributes in this file: [default_attributes.xml](/uploads/fceeb696327b99b1dcddac57993d417a/default_attributes.xml))
Here's a screenshot on how we set these attributes in the Function Type:
![interface-attributes](/uploads/c37fcb270782487e7ca129dfc07e86a7/interface-attributes.png)
The problem is: when we set these interface attributes on the Function Type named "ComponentType" as you can see in the screenshot, these get not inherited by the corresponding instance Function named "Instance".
Here's a zipped TASTE project folder named "attributes" with the minimal example shown above: [attributes.zip](/uploads/bd2177617715b959f72f10c3374ead34/attributes.zip)
As a final note, I report we had a related issue on another TASTE model (which unfortunately is too complex to be shared here at the moment). In this last case, the attributes got instead inherited correctly by the instances and set correctly in the interfaceview.xml file. However, in the resulting InterfaceView.aadl, the instance functions had these attributes (is_alarm and is_observables) always set to "false" even though in the interfaceview.xml they were set to "true".Maxime PerrotinMaxime Perrotinhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/788When an interface has OUT params, make it visible in the IV2024-03-20T08:50:35ZMaxime PerrotinWhen an interface has OUT params, make it visible in the IVFor readability purposes it would be useful to show a little arrow indicating that a PI contains an OUT parameter, e.g. below the connection line.For readability purposes it would be useful to show a little arrow indicating that a PI contains an OUT parameter, e.g. below the connection line.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/759IVE DVE Store default values in xml files2021-12-21T15:45:12ZGuenter SchwannIVE DVE Store default values in xml filesWhen there is a default value set for an attribute, and it is unchanged, at the moment you do not save the attribute in the templates (interfaceview and dataview xml files).
![image](/uploads/d52463f189390347e9a4908c6642dfad/image.png)
...When there is a default value set for an attribute, and it is unchanged, at the moment you do not save the attribute in the templates (interfaceview and dataview xml files).
![image](/uploads/d52463f189390347e9a4908c6642dfad/image.png)
We should save the value in any case (so the value is available in the XML).https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/739IVE: Centering view is preformed in the scene when QtCreator opens another file2022-12-07T07:18:44ZAlex DievIVE: Centering view is preformed in the scene when QtCreator opens another filehttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/737IVE: Simplify geometry update in controller part2023-11-20T14:18:44ZAlex DievIVE: Simplify geometry update in controller parthttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/736IVE: Wrong mini view rendering2024-03-20T10:11:27ZAlex DievIVE: Wrong mini view rendering![image](/uploads/0f4fbef406bc207480069b676ff09fbe/image.png)
[ergo.zip](/uploads/c9e8743ad6fc60e5f00daa0ea81f20c4/ergo.zip)![image](/uploads/0f4fbef406bc207480069b676ff09fbe/image.png)
[ergo.zip](/uploads/c9e8743ad6fc60e5f00daa0ea81f20c4/ergo.zip)Denis GofmanDenis Gofmanhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/697IVE: Check for more dependencies on attribute changes2023-12-05T09:48:31ZGuenter SchwannIVE: Check for more dependencies on attribute changesIn Issue #692 the attributes are updated when the user changes one attribute.
But for each changed attribute, another check (for dependent attributes) should be performed.
For example the interface `kind` change triggers the `miat`. An...In Issue #692 the attributes are updated when the user changes one attribute.
But for each changed attribute, another check (for dependent attributes) should be performed.
For example the interface `kind` change triggers the `miat`. And this automatic change of `miat` might trigger another attribute.