SpaceCreator issueshttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues2021-03-31T13:41:20Zhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/1Function named "Source" seems to cause issues which are not communicated in a...2021-03-31T13:41:20ZMichal KurowskiFunction named "Source" seems to cause issues which are not communicated in a clear way.**Steps to reproduce:**
1. Create InterfaceView with an SDL function called Source.
1. Try to edit the function.
**What happens:**
1. The following error message is presented to the user.
```
InterfaceView.aadl:8:23: parsing Package_Nam...**Steps to reproduce:**
1. Create InterfaceView with an SDL function called Source.
1. Try to edit the function.
**What happens:**
1. The following error message is presented to the user.
```
InterfaceView.aadl:8:23: parsing Package_Name, list is empty
InterfaceView.aadl:8:31: parsing Import_Declaration, unexpected token ';'
InterfaceView.aadl:8:31: parsing Name_Visibility_Declaration, unexpected token ';'
InterfaceView.aadl:12:39: parsing Parameter, token ';' is expected, found token '-'
InterfaceView.aadl:11:01: parsing Features, list is empty
InterfaceView.aadl:26:37: parsing Parameter, token ';' is expected, found token '-'
InterfaceView.aadl:25:01: parsing Features, list is empty
InterfaceView.aadl:50:65: parsing Subcomponent_Access_Classifier, an identifier is expected, found keyword 'source'
```
**What is expected:**
Clear and visible communication in the IDE that the "Source" is a reserved keyword. If possible, an average TASTE user should not be concerned with the pecularities of AADL, as it is hidden behind the scenes. Also, some keywords seem like good names, at least for demonstration/educational purposes.
This may also affect other keywords.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/2:-1: error: /usr/lib/x86_64-linux-gnu/qtcreator/libexec/asn1scc/asn1.exe: Com...2023-09-13T07:59:28ZMichal Kurowski:-1: error: /usr/lib/x86_64-linux-gnu/qtcreator/libexec/asn1scc/asn1.exe: Command not found**Steps to reproduce:**
1. In the projects widget, right click on the ${PROJECT_NAME}.asn file and select Build from the context menu.
**What happens:**
1. The following error is shown:
`error: /usr/lib/x86_64-linux-gnu/qtcreator/libexe...**Steps to reproduce:**
1. In the projects widget, right click on the ${PROJECT_NAME}.asn file and select Build from the context menu.
**What happens:**
1. The following error is shown:
`error: /usr/lib/x86_64-linux-gnu/qtcreator/libexec/asn1scc/asn1.exe: Command not found`
**What should happen:**
1. Error message should not be shown, unless there is a problem with the ASN.1 file
1. [option] nothing - maybe the action should be hidden?
1. [option] compile - but then, to what target (C, Ada, ICD,...) - maybe there should be multiple actions, or a dialog?
1. [option] update the DataView (does this happen automatically?)
The compiler path found under Tools->Options->SpaceCreator->Compiler does not seem to affect this error. Should there be another path option?https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/3ASN.1 types with a hyphen in the name are not supported2021-02-17T15:13:46ZMichal KurowskiASN.1 types with a hyphen in the name are not supported**Steps to reproduce:**
1. Create an ASN.1 type with a hyphen in the name, like My-Type ::= INTEGER(0..100)
1. Use the ASN.1 type as an interface parameter in a function
1. Try to edit the function or build the system
**What happens:**
...**Steps to reproduce:**
1. Create an ASN.1 type with a hyphen in the name, like My-Type ::= INTEGER(0..100)
1. Use the ASN.1 type as an interface parameter in a function
1. Try to edit the function or build the system
**What happens:**
1. When trying to edit the function, a window pops up and closes very fast
1. When trying to build the system, the following error is reported:
```
InterfaceView.aadl:11:37: parsing Parameter, token ';' is expected, found token '-'
InterfaceView.aadl:10:01: parsing Features, list is empty
InterfaceView.aadl:43:38: parsing Package_Specification, Empty packages are not allowed
InterfaceView.aadl:58:39: parsing Parameter, token ';' is expected, found token '-'
InterfaceView.aadl:57:01: parsing Features, list is empty
InterfaceView.aadl:72:37: parsing Parameter, token ';' is expected, found token '-'
InterfaceView.aadl:71:01: parsing Features, list is empty
InterfaceView.aadl:114:37: parsing Package_Specification, Empty packages are not allowed
InterfaceView.aadl:128:39: parsing Parameter, token ';' is expected, found token '-'
InterfaceView.aadl:127:01: parsing Features, list is empty
InterfaceView.aadl:161:43: parsing Package_Specification, Empty packages are not allowed
```
**What should happen:**
1. Valid ASN.1 type names should be allowed for use (proper translation to AADL compliant names should be provided)
1. When trying to edit a function, an appropriate editor should be launched, unless there are other issues. If the editor cannot be launched, a clear, readable error message should be presented to the user.
1. When trying to build the system, the system should build, unless there are other issues.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/595IVE: Export all asn data2021-11-10T13:27:08ZGuenter SchwannIVE: Export all asn dataOn export, ALL the .asn1, .acn, and .asn of the current project (listed in the .pro) shall be exported.On export, ALL the .asn1, .acn, and .asn of the current project (listed in the .pro) shall be exported.Alex DievAlex Dievhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/597IVE: Fix exported structure2021-11-10T13:27:05ZGuenter SchwannIVE: Fix exported structureThere is an issue with the export directory structure as you can see in the screenshot: you have "SimpleFunction" and at the next level "work/simplefunction". I think the implementation of SimpleFunction (work) should be below SimpleFunc...There is an issue with the export directory structure as you can see in the screenshot: you have "SimpleFunction" and at the next level "work/simplefunction". I think the implementation of SimpleFunction (work) should be below SimpleFunction
![image](/uploads/cfaad2f04cf2935757dfa3b0cd27aeef/image.png)Alex DievAlex Dievhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/598IVE: Importing all asn data2021-11-10T13:27:05ZGuenter SchwannIVE: Importing all asn dataFunction import: you do not import the ASN.1 files, instead you should try to import them all, with the following rules
- [ ] copy the ASN.1 and ACN files to the current project folder and add them to the .pro file
- [ ] if filename alr...Function import: you do not import the ASN.1 files, instead you should try to import them all, with the following rules
- [ ] copy the ASN.1 and ACN files to the current project folder and add them to the .pro file
- [ ] if filename already exists: propose to rename the file or ignore it
- [ ] for each ASN.1 module in the ASN.1 files, if an identical module name already exists in the current system, warn the user and propose to a) add it anyway, b) ignore the file containing the module
The list of ASN.1 modules is in the XML AST of the ASN.1 file that you parse (ASN.1 files start with "ModuleName DEFINITIONS ::= ...."Alex DievAlex Dievhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/699IVE: Changing the interface kind selects all attributes2021-10-19T21:55:39ZGuenter SchwannIVE: Changing the interface kind selects all attributesWhen you change an interface kind, all values are "selected" :
![image](/uploads/9936094c14fa7589460200e58c960e88/image.png)When you change an interface kind, all values are "selected" :
![image](/uploads/9936094c14fa7589460200e58c960e88/image.png)Alex DievAlex Dievhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/781MSC Editor - ASN1 Value missing field name2022-11-09T10:56:36ZMaxime PerrotinMSC Editor - ASN1 Value missing field nameOpen the attached MSC and try to edit the message parameters.
There are two parameters, one of type Seq1 (which is fine) and one of type `Seq2`.
The second one does not show the name of the second field (`f2`) of the SEQUENCE:
![image]...Open the attached MSC and try to edit the message parameters.
There are two parameters, one of type Seq1 (which is fine) and one of type `Seq2`.
The second one does not show the name of the second field (`f2`) of the SEQUENCE:
![image](/uploads/6cad9faccce3f65d89fd587ab6dd4791/image.png)
While it is properly defined in the ASN.1 model:
![image](/uploads/47289fd7cc447d7d404fc2ff9f4cb45e/image.png)
It makes it impossible to generate a valid MSC syntax.
[dv.asn](/uploads/bcdda8f02f2a784e7f9f577efb092fa0/dv.asn)[foo.msc](/uploads/8a88afd19d8a35d10f5b7eb079627789/foo.msc)14 Fix issues reported in gitlabGuenter SchwannGuenter Schwannhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/844IVE: Fix QProcess call in ModelCheckingWindow2022-11-15T12:50:51ZGuenter SchwannIVE: Fix QProcess call in ModelCheckingWindow- [x] In ModelCheckingWindow `QProcess::execute()` is still using the Qt5 API. A split into command and arguments is needed.
- [x] Check the whole code for more old QProcess usages
- [ ] extprocmonitor.cpp
- [ ] asn1reader.cpp
- [...- [x] In ModelCheckingWindow `QProcess::execute()` is still using the Qt5 API. A split into command and arguments is needed.
- [x] Check the whole code for more old QProcess usages
- [ ] extprocmonitor.cpp
- [ ] asn1reader.cpp
- [ ] tmc::converter.cpp
- [ ] sdltopromela::converter
- [ ] verifier.cpp
- [ ] simulinkimporterplugin.cpp
- [x] Make the ASN.1 highlight work (install .xml files, even if asn plugin is disabled)
- [x] QtCreator4.8 uses `share/qtcreator/generic-highlighter`
- [ ] QtCreator8 uses `share/qtcreator/generic-highlighter/syntax`
- [ ] Update Readme.md to point to quickstart.md
- [ ] Remove unused script files (shell script in "scripts" folder)2 Update to latest QCreatorKasper FiskerKasper Fiskerhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/782Segfault when closing then reopening an MSC in Space Creator2022-11-10T09:31:12ZMaxime PerrotinSegfault when closing then reopening an MSC in Space CreatorOpen this MSC (or any other) in the MSC Editor inside QtCreator (NOT the standalone tool)
[foo.msc](/uploads/f9782cf5343b7225f16070c92954822d/foo.msc)
Close it with this button:
![image](/uploads/021966f6e5f76784fefd78a7a26d4330/image....Open this MSC (or any other) in the MSC Editor inside QtCreator (NOT the standalone tool)
[foo.msc](/uploads/f9782cf5343b7225f16070c92954822d/foo.msc)
Close it with this button:
![image](/uploads/021966f6e5f76784fefd78a7a26d4330/image.png)
Then try to open it again like this:
![image](/uploads/79e5aa578fe89cb7a6ddb393c56b8421/image.png)
It segfaults immediatly.8 Improve MSC editor and streamerGuenter SchwannGuenter Schwannhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/771IVE: Not all ASN.1 file are used2022-12-12T15:21:33ZGuenter SchwannIVE: Not all ASN.1 file are used![image](/uploads/1c88911372dea3fcf0f99746475ffc54/image.png)
The tool reports an error saying that T-UInt32 is not defined, however it is defined in "taste-types.asn" that is listed as a .asn file in the .pro file
It seems that when...![image](/uploads/1c88911372dea3fcf0f99746475ffc54/image.png)
The tool reports an error saying that T-UInt32 is not defined, however it is defined in "taste-types.asn" that is listed as a .asn file in the .pro file
It seems that when you call asn1scc you still don't pass properly all the asn1 files
Because of this parsing error, none of the types from this module are visible in the interfaces of the system
... Except those defined in taste-types.asn! That's confusing
![image](/uploads/8df0772eedee8cfa34e3ee891ac97b21/image.png)
Example demonstrating the issue: [asn1Issues.zip](/uploads/c7a8644edf8b0322b16135bc119d4364/asn1Issues.zip)
If you look at the .pro files you'll see the 3 asn1 files listed, but if you open the model, the parsing of the one that uses the IMPORT from another one of the file fails. Note one of the files is in a remote folder, that exists in the TASTE VM14 Fix issues reported in gitlabGuenter SchwannGuenter Schwannhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/834IVE: Mini view is too big2022-11-14T11:28:23ZGuenter SchwannIVE: Mini view is too bigWeird situation where the mini-view is actually bigger than the main view:
![image](/uploads/b15a16765ae9624e17eef77420972246/image.png)
[interfaceview.xml](/uploads/0c72be005d04a222bcb2d055d78a3a17/interfaceview.xml)
The issue is, th...Weird situation where the mini-view is actually bigger than the main view:
![image](/uploads/b15a16765ae9624e17eef77420972246/image.png)
[interfaceview.xml](/uploads/0c72be005d04a222bcb2d055d78a3a17/interfaceview.xml)
The issue is, that the height is only limited by the height of the editor. But should be the same as the wideth.
So the the mini-view should be fit in a square box (width and height be the same as the current width).14 Fix issues reported in gitlabAlejandro ExojoAlejandro Exojohttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/825IVE: HTML tags shown when Qt6 is used2022-11-09T10:57:26ZGuenter SchwannIVE: HTML tags shown when Qt6 is usedWhen using Qt6 / QtCreator 8, HTML tags are show in function names:<br>
![image](/uploads/fedeed1eee31797ffa8409bdddf6afe8/image.png)When using Qt6 / QtCreator 8, HTML tags are show in function names:<br>
![image](/uploads/fedeed1eee31797ffa8409bdddf6afe8/image.png)2 Update to latest QCreatorAlex DievAlex Dievhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/770IVE: Shared import ignore the asn.1 files2022-11-09T10:57:39ZGuenter SchwannIVE: Shared import ignore the asn.1 filesWhen you instantiate a function type from the shared types, the ASN.1 is **not imported** to the current project as it should (same mechanism as the import of component)When you instantiate a function type from the shared types, the ASN.1 is **not imported** to the current project as it should (same mechanism as the import of component)6 Manage library of componentshttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/776IVE: default_properties.xml file issues2023-04-26T08:50:03ZGuenter SchwannIVE: default_properties.xml file issuesHi, I think there is a major bug in the loading of the default_properties.xml file
Apparently the tool is looking for the property file first in `~/.local/share/ESA/` folder, while the user-defined property file is located in `~/.local/...Hi, I think there is a major bug in the loading of the default_properties.xml file
Apparently the tool is looking for the property file first in `~/.local/share/ESA/` folder, while the user-defined property file is located in `~/.local/share/QtProject/QtCreator`
It seems that the first time Space creator is launched, the file is copied in share/ESA folder, and never updated afterwards
So if the one is qtproject folder changes, the changes are not read/applied.
Question is : what is this ESA folder and why do we need it?
Can we delete it safely when installing a new version of Space Creator ?
On one of our VM the issue was really difficult to debug. The `default_attributes.xml` that we provide was not properly taken into account (only partially: only the parts that were not already covered by the version in the share/ESA folder), so a value was not generated in interfaceview.xml - while it was in a fresh VM.
The reason was that the version in share/ESA was placed there by an older version of Space creator and apparently is never updated once it has been copied. So it would always remain wrong.14 Fix issues reported in gitlabGuenter SchwannGuenter Schwannhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/769IVE: Deprecated Language attribute isn't removed with new implementation2023-03-06T14:58:12ZAlex DievIVE: Deprecated Language attribute isn't removed with new implementationWhen a model done from a previous version of space creator contains a function type, it may still have the attribute "language="SDL"" and not the "type_language" attribute.
If you open the model and save it with the latest versions of sp...When a model done from a previous version of space creator contains a function type, it may still have the attribute "language="SDL"" and not the "type_language" attribute.
If you open the model and save it with the latest versions of space creator it will properly add type_language, but it will not remove language=SDL as it shouldGuenter SchwannGuenter Schwannhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/774IVE: Deleting nested function doesn't remove it from the XML file2022-11-09T10:59:44ZFilip DemskiIVE: Deleting nested function doesn't remove it from the XML file## Steps to reproduce:
1. Create a function
2. Create a nested function in the other one
3. Save model
4. Delete the nested function
5. Save model
6. Open `interfaceview.xml` as a plain text
7. Nested function still present
8. Restart S...## Steps to reproduce:
1. Create a function
2. Create a nested function in the other one
3. Save model
4. Delete the nested function
5. Save model
6. Open `interfaceview.xml` as a plain text
7. Nested function still present
8. Restart SpaceCreator
9. Nested function is present in the model14 Fix issues reported in gitlabhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/1085Use QString instead of QByteArray in qgitlab/requirements2023-12-06T10:24:30ZGuenter SchwannUse QString instead of QByteArray in qgitlab/requirementsFor easier usage (keep in sync with majority of Qt's API) use `QString` instead of `QByteArray`. For example for the requirements IDs.
`RequirementsModel::setData()` can be simplified a bit as well then.For easier usage (keep in sync with majority of Qt's API) use `QString` instead of `QByteArray`. For example for the requirements IDs.
`RequirementsModel::setData()` can be simplified a bit as well then.1 Traceability - RequirementsHugo Jiménez HernándezHugo Jiménez Hernándezhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/1068Bug in MiniMap's transparency management2024-03-20T08:52:24ZDenis GofmanBug in MiniMap's transparency managementThe MM's transparency management provided by #1047 resulted in an issue:
Restoring its opaqueness on mouse hover works only if the mouse enters the MM over an item and doesn't work if the mouse follows an empty scene area.
![minimap_bug...The MM's transparency management provided by #1047 resulted in an issue:
Restoring its opaqueness on mouse hover works only if the mouse enters the MM over an item and doesn't work if the mouse follows an empty scene area.
![minimap_bug](/uploads/ba5461be6e4cc37d94494b94237c8f31/minimap_bug.gif)Denis GofmanDenis Gofmanhttps://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/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/791Color issues wiht QtC in dark theme2023-04-26T10:08:01ZGuenter SchwannColor issues wiht QtC in dark themeTetx of interfaces are invisible:
![image](/uploads/b9ef36254df7c26cc0c2295ef7c20b83/image.png)
Text of layers, IV structure etc. is hard to read:
![image](/uploads/d33b9c73aae0a7ab73b1b7e93f2ab370/image.png)Tetx of interfaces are invisible:
![image](/uploads/b9ef36254df7c26cc0c2295ef7c20b83/image.png)
Text of layers, IV structure etc. is hard to read:
![image](/uploads/d33b9c73aae0a7ab73b1b7e93f2ab370/image.png)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/618Check to get stack trace on crashes2021-11-18T13:30:27ZGuenter SchwannCheck to get stack trace on crashesIn order to help with crash reports, could you look at the possibilty to dump the call stack when an exception happens - for example using this approach :
https://stackoverflow.com/questions/77005/how-to-automatically-generate-a-stacktr...In order to help with crash reports, could you look at the possibilty to dump the call stack when an exception happens - for example using this approach :
https://stackoverflow.com/questions/77005/how-to-automatically-generate-a-stacktrace-when-my-program-crashes
(or anything better you may know of)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/560IVE: Renaming a function type does not rename it's references2021-07-06T10:46:26ZGuenter SchwannIVE: Renaming a function type does not rename it's referencesSteps to reproduce:
* Create a new IV file
* Add a function type
* Add a function that is type of the function type
* Rename the function type
* Save to a file
-> The "type of" reference in the file is using the old name
-> In the fun...Steps to reproduce:
* Create a new IV file
* Add a function type
* Add a function that is type of the function type
* Rename the function type
* Save to a file
-> The "type of" reference in the file is using the old name
-> In the function preference dialog, the reference is losthttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/492IVE: Creating a function shall focus and select the name2021-04-26T05:37:55ZGuenter SchwannIVE: Creating a function shall focus and select the nameCreating a function shall focus and select the name in the graphics item directly. For easy and fast workflow.Creating a function shall focus and select the name in the graphics item directly. For easy and fast workflow.DVE_01Alex DievAlex Dievhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/484IVE: Interface move might wrongly grab the connection2021-04-23T08:59:00ZGuenter SchwannIVE: Interface move might wrongly grab the connectionI noticed also a small glitch in the interface selection to move it. Depending on where you click inside the triangle itself, it will either move the interface around the box, or select the connection and detach it from the box to move (...I noticed also a small glitch in the interface selection to move it. Depending on where you click inside the triangle itself, it will either move the interface around the box, or select the connection and detach it from the box to move (and re-compute the shape at the end)
Actually from usage I prefer the second case : when you select an interface, I think it is better to always detach it and re-compute the points when it is dropped again
![grab](/uploads/ded2ca913492ec555ddc5c47a2397223/grab.gif)DVE_01Alex DievAlex Dievhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/6Create a single application with both the VS editors in2021-03-31T13:48:27ZMaxime PerrotinCreate a single application with both the VS editors inJust get to the first stepJust get to the first stephttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/7Refactor the two VS editors to a shared inheritance tree2021-03-31T13:48:27ZMaxime PerrotinRefactor the two VS editors to a shared inheritance treehttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/8Import the two VS editor source trees2021-03-31T13:48:27ZMaxime PerrotinImport the two VS editor source treesMake sure to tag (or something) the version imported in all three.Make sure to tag (or something) the version imported in all three.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/9Set up CI2021-03-31T13:52:40ZMaxime PerrotinSet up CI* [x] Enable Gitlab CI
* [x] Create new Docker image (Debian 10, Java, grantlee, QtCreator, cmake, ninja, ccache, ...)
* [x] Build SpaceCreator for Debian 10
* [x] Run unit tests
* [ ] Add Windows 10 build* [x] Enable Gitlab CI
* [x] Create new Docker image (Debian 10, Java, grantlee, QtCreator, cmake, ninja, ccache, ...)
* [x] Build SpaceCreator for Debian 10
* [x] Run unit tests
* [ ] Add Windows 10 buildhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/10Create build instructions2021-03-31T13:52:40ZMaxime PerrotinCreate build instructionshttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/11Create dependency list2021-03-31T13:52:40ZMaxime PerrotinCreate dependency listhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/12Save MSC files using grantlee2021-03-31T13:52:40ZMaxime PerrotinSave MSC files using grantleeAdd the same templating engine to the MSC editor as the
IV editor uses for transforming the models to code or test
scripts
* [x] Learn about grantlee
* [x] Check about IV editor implementation
* [x] Add second code path to store a ver...Add the same templating engine to the MSC editor as the
IV editor uses for transforming the models to code or test
scripts
* [x] Learn about grantlee
* [x] Check about IV editor implementation
* [x] Add second code path to store a very basic msc document
* [x] Add chart
* [x] Add instance
* [x] Add message
* [x] Add action
* [x] Add comment
* [x] Add coregion
* [x] Add timer
* [x] Add create
* [x] Add condition
* [x] Add Cif information
* [x] Add Cif information for comments
* [x] Add global commenthttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/13Mirror repo?2021-03-31T13:52:40ZMaxime PerrotinMirror repo?Find out if Maxime wants the repo mirrored at the ESA git server, and if so, do it.Find out if Maxime wants the repo mirrored at the ESA git server, and if so, do it.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/14Create a set of test MSC files2021-03-31T13:52:40ZMaxime PerrotinCreate a set of test MSC filesMaxime should give us some test files and we can create some moreMaxime should give us some test files and we can create some morehttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/15Copy the 7 Space code2021-03-31T13:52:40ZMaxime PerrotinCopy the 7 Space codeCopy this into our repo. This doesn't mean incorporating it in the code yet.Copy this into our repo. This doesn't mean incorporating it in the code yet.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/16Create a reasonable source tree2021-03-31T13:52:40ZMaxime PerrotinCreate a reasonable source treeMove stuff from the two VS apps repos to /src/{libs,apps,tests...}Move stuff from the two VS apps repos to /src/{libs,apps,tests...}https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/17Create CMake build system2021-03-31T13:52:41ZMaxime PerrotinCreate CMake build systemhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/18Split IV editor to have stuff in libs2021-03-31T13:52:41ZMaxime PerrotinSplit IV editor to have stuff in libshttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/19Get rid of the antlr build scripts and do this in cmake instead2021-03-31T13:52:41ZMaxime PerrotinGet rid of the antlr build scripts and do this in cmake insteadhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/20Build the antlr runtime during our own build instead of providing prebuilt bi...2021-03-31T13:52:41ZMaxime PerrotinBuild the antlr runtime during our own build instead of providing prebuilt binaries in the src treeThis means getting rid of the bat and sh files to create this, and do it directly in cmake.
The current msclibrary/CMakeLists.txt has this list of files created by ANTLR:
set(ANTLR_SRC
parser/MscBaseVisitor.h
parser/MscLexer.h
...This means getting rid of the bat and sh files to create this, and do it directly in cmake.
The current msclibrary/CMakeLists.txt has this list of files created by ANTLR:
set(ANTLR_SRC
parser/MscBaseVisitor.h
parser/MscLexer.h
parser/MscParser.h
parser/MscVisitor.h
parser/MscBaseVisitor.cpp
parser/MscLexer.cpp
parser/MscParser.cpp
parser/MscVisitor.cpp
)
These should be placed in the build directory, not in the source directory.
And the files should be removed from the .gitignore.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/21Build with new updated antlr2021-03-31T13:52:41ZMaxime PerrotinBuild with new updated antlr'- Move 3rdparty dir to /src
- Update to 4.8
- Copy the runtime sources from the original site
- Leave the current 4.7 until we know the one works
- Remove the current subdir for antlr and add the new one'- Move 3rdparty dir to /src
- Update to 4.8
- Copy the runtime sources from the original site
- Leave the current 4.7 until we know the one works
- Remove the current subdir for antlr and add the new onehttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/22Remove old antlr version2021-03-31T13:52:41ZMaxime PerrotinRemove old antlr versionhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/23Fix resetting settings to the default value2021-03-31T13:52:41ZMaxime PerrotinFix resetting settings to the default valueIn SettingsAppOptions::write there is a test for whether something is the default value. This seems to be wrong. If you save a new value and later want to save the default value, you can't.In SettingsAppOptions::write there is a test for whether something is the default value. This seems to be wrong. If you save a new value and later want to save the default value, you can't.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/24Create a base class for the GraphicsView use of both apps2021-03-31T13:52:41ZMaxime PerrotinCreate a base class for the GraphicsView use of both apps... and use it in the apps
Add the zoom controller as well... and use it in the apps
Add the zoom controller as wellhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/25Move MSC editor command line handling to the shared library2021-03-31T13:52:41ZMaxime PerrotinMove MSC editor command line handling to the shared libraryhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/26Refactor IV editor to use the shared command line class2021-03-31T13:52:41ZMaxime PerrotinRefactor IV editor to use the shared command line classhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/27Fix IV editor tests2021-04-02T10:50:48ZMaxime PerrotinFix IV editor testshttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/28Investigate undo/redo in the two apps and come up with ideas2021-04-02T10:50:49ZMaxime PerrotinInvestigate undo/redo in the two apps and come up with ideashttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/29Unify log handling in the shared lib or remove it2021-04-02T10:50:49ZMaxime PerrotinUnify log handling in the shared lib or remove ithttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/30Add issues from taste3 and msc editor issue trackers2021-04-02T10:50:49ZMaxime PerrotinAdd issues from taste3 and msc editor issue trackershttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/31Handle menus in IVeditor like in MSC editor and merge them2021-04-02T10:50:50ZMaxime PerrotinHandle menus in IVeditor like in MSC editor and merge themhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/32Create a toolbar base class2021-04-02T10:50:50ZMaxime PerrotinCreate a toolbar base classhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/33Create the interface/module handler2021-04-02T10:50:50ZMaxime PerrotinCreate the interface/module handlerThis is the system that switches between the modes of the application, and the one that shows the proper toolbar/view/menu entries ...This is the system that switches between the modes of the application, and the one that shows the proper toolbar/view/menu entries ...https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/34Create a sprint/progress report2021-04-02T10:50:50ZMaxime PerrotinCreate a sprint/progress reportSend it to Maxime prior to the meetingSend it to Maxime prior to the meetinghttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/35MSC: The MainWindow options processing2021-04-02T10:50:50ZMaxime PerrotinMSC: The MainWindow options processingIt seems there is a typo in https://git.vikingsoftware.com/esa/msceditor/blob/master/msceditor/mainwindow.cpp#L904
(`break;` vs `return true;`):
```
case CommandLineParser::Positional::DropUnsavedChangesSilently: {
d->m_dropUns...It seems there is a typo in https://git.vikingsoftware.com/esa/msceditor/blob/master/msceditor/mainwindow.cpp#L904
(`break;` vs `return true;`):
```
case CommandLineParser::Positional::DropUnsavedChangesSilently: {
d->m_dropUnsavedChangesSilently = true;
return true;
}
```https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/36MSC: Arrow size box from right to left is wrong2021-04-02T10:50:50ZMaxime PerrotinMSC: Arrow size box from right to left is wrongThis also affect the arrow coordinates in the backend, with this issue the coordinates of the arrow start at the margin instead of at the edge, left to right is unaffected
![image](/uploads/264ea0b8eaa56003be2a509dc91a54f9/image.png)This also affect the arrow coordinates in the backend, with this issue the coordinates of the arrow start at the margin instead of at the edge, left to right is unaffected
![image](/uploads/264ea0b8eaa56003be2a509dc91a54f9/image.png)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/37MSC: Resizing of ACTION text box is not consistent2021-04-02T10:50:50ZMaxime PerrotinMSC: Resizing of ACTION text box is not consistentVarious issues with ACTION boxes, as seen on the picture :
![image](/uploads/429e380ed21067d2fd7388f6cff306ee/image.png)Various issues with ACTION boxes, as seen on the picture :
![image](/uploads/429e380ed21067d2fd7388f6cff306ee/image.png)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/38MSC: Action name input is not verified2021-04-02T10:50:50ZMaxime PerrotinMSC: Action name input is not verifiedOnly limited set of characters are allowed
To reproduce:
create an instance and put an action on it, name the action something like ?///-=04=3-5904539065ujo;trhyarotg'na'sd"""''''''';';';""'' it will be accepted. The text will turn redOnly limited set of characters are allowed
To reproduce:
create an instance and put an action on it, name the action something like ?///-=04=3-5904539065ujo;trhyarotg'na'sd"""''''''';';';""'' it will be accepted. The text will turn redhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/39MSC: Issue with coregions2021-04-02T10:50:50ZMaxime PerrotinMSC: Issue with coregionsCreate two instances with a message in a coregion:
![image](/uploads/4f46d9b8ee559d97a2161f9d376a5880/image.png)
If you move the head or the tail of the message, it sometimes goes out of the coregion and makes the coregion zone move up...Create two instances with a message in a coregion:
![image](/uploads/4f46d9b8ee559d97a2161f9d376a5880/image.png)
If you move the head or the tail of the message, it sometimes goes out of the coregion and makes the coregion zone move up in the diagram
![image](/uploads/9e102be0d88832927c87c57912bfad51/image.png)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/40AADL: Comment rendering2021-04-02T10:50:51ZMaxime PerrotinAADL: Comment rendering'- [x] No line breaks yet;
- [x] Text is not updated after closing the editor.'- [x] No line breaks yet;
- [x] Text is not updated after closing the editor.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/41AADL: Comments should be above connections2021-04-02T10:50:50ZMaxime PerrotinAADL: Comments should be above connectionshttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/42AADL: Moving interfaces2021-04-02T10:50:51ZMaxime PerrotinAADL: Moving interfacesRight now we have to first select and then move an interface. It should be movable immediatelyRight now we have to first select and then move an interface. It should be movable immediatelyhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/43AADL: Interfaces can become locked to a position2021-04-02T10:50:50ZMaxime PerrotinAADL: Interfaces can become locked to a positionhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/44AADL: Corner connections is wrong2021-04-02T10:50:51ZMaxime PerrotinAADL: Corner connections is wronghttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/45AADL: Comment text storing2021-04-02T10:51:16ZMaxime PerrotinAADL: Comment text storingSince the text is not validated now, it's possible to break the XML stream with something like `<!-- <Function name="pwnd"\n\`.
Obviously, the encoding on writing and decoding on reading is necessary, also to keep the line breaks and so...Since the text is not validated now, it's possible to break the XML stream with something like `<!-- <Function name="pwnd"\n\`.
Obviously, the encoding on writing and decoding on reading is necessary, also to keep the line breaks and so on. But I'm not sure what to use exactly - base64? url-encoding? CDATA?https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/46Add AADL grantlee unit tests for saving2021-04-02T10:51:15ZMaxime PerrotinAdd AADL grantlee unit tests for savinghttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/47Build the documentation in the CI2021-04-02T10:51:15ZMaxime PerrotinBuild the documentation in the CIhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/48Switch to doxygen2021-04-02T10:51:15ZMaxime PerrotinSwitch to doxygenThis will require rewriting some of the current documentationThis will require rewriting some of the current documentationhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/49Move all class documentation to header files2021-04-02T10:51:16ZMaxime PerrotinMove all class documentation to header fileshttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/50Replace the two image backgrounds code2021-04-02T10:51:16ZMaxime PerrotinReplace the two image backgrounds codeInstead of painting background images on GraphicsView objects, replace it with a proper painter in GraphicsViewBaseInstead of painting background images on GraphicsView objects, replace it with a proper painter in GraphicsViewBasehttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/51IV editor does not load resource2021-04-02T10:51:16ZMaxime PerrotinIV editor does not load resourcehttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/52Place binaries in builddir/bin2021-04-02T10:51:16ZMaxime PerrotinPlace binaries in builddir/binTo make it easier to run the applications outside of QtCreator, place the executables in builddir/bin.To make it easier to run the applications outside of QtCreator, place the executables in builddir/bin.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/53Add command line option for conversion2021-04-02T10:51:16ZMaxime PerrotinAdd command line option for conversionMSC editor should have a parameter so it is possible to select a template and a .msc file, to convert (load and save) the .msc file.
No UI should be shown in that case.MSC editor should have a parameter so it is possible to select a template and a .msc file, to convert (load and save) the .msc file.
No UI should be shown in that case.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/54Unable to add a global comment2021-04-02T10:51:16ZMaxime PerrotinUnable to add a global commentThe global comment can be selected in MSC editor, but it is not possible to drop/place/select it.The global comment can be selected in MSC editor, but it is not possible to drop/place/select it.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/55The text of a comment can't be changed2021-04-02T10:51:16ZMaxime PerrotinThe text of a comment can't be changedAfter editing the text of a comment, the original comment re-appears again.After editing the text of a comment, the original comment re-appears again.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/56Add aadl options to the command line unit test2021-04-02T10:51:16ZMaxime PerrotinAdd aadl options to the command line unit testhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/57Check and fix namespaces2021-04-02T10:51:16ZMaxime PerrotinCheck and fix namespacesThe doxygen documentation gives a nice overview to check the namespaces.
They should be consistent.The doxygen documentation gives a nice overview to check the namespaces.
They should be consistent.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/58Check read/load name consistencies2021-04-02T10:51:17ZMaxime PerrotinCheck read/load name consistenciesMSC editor has `msc::MscFile` to load .msc files. And `msc::MscWriter` for saving.
IV editor has `aadl::AADLXMLReader` and `taste3::app:XmlDocExporter`MSC editor has `msc::MscFile` to load .msc files. And `msc::MscWriter` for saving.
IV editor has `aadl::AADLXMLReader` and `taste3::app:XmlDocExporter`https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/59Add a base widget for the mainwindow contents2021-04-02T10:51:16ZMaxime PerrotinAdd a base widget for the mainwindow contentsAlso, create the subclasses in the IV and MSC editors. The goal of this is to get rid of the two mainwindow subclasses.Also, create the subclasses in the IV and MSC editors. The goal of this is to get rid of the two mainwindow subclasses.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/60Change the application library name to libmsceditor2021-04-02T10:51:16ZMaxime PerrotinChange the application library name to libmsceditorhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/61Starting msc editor shows a warning2021-04-02T10:51:17ZMaxime PerrotinStarting msc editor shows a warningWarning `QObject::connect(QAction, msc::MainWindow): invalid null parameter` is shown on meseditor startup.Warning `QObject::connect(QAction, msc::MainWindow): invalid null parameter` is shown on meseditor startup.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/62Build ASN.1 editor2021-04-02T10:51:17ZMaxime PerrotinBuild ASN.1 editor* [x] Create cmake project file
* [x] Build creator plugin in CI
~~* [ ] Extract library (or libraries?)~~ is done in #58
* [ ] Move tests to common tests directory* [x] Create cmake project file
* [x] Build creator plugin in CI
~~* [ ] Extract library (or libraries?)~~ is done in #58
* [ ] Move tests to common tests directoryhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/63Split ASN.1 file handling into a library2021-04-02T10:51:32ZMaxime PerrotinSplit ASN.1 file handling into a libraryhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/64Write a high level architecture overview document2021-04-02T10:51:32ZMaxime PerrotinWrite a high level architecture overview documenthttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/65Create a test document2021-04-02T10:51:32ZMaxime PerrotinCreate a test documentAdd the first 5 test casesAdd the first 5 test caseshttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/66Merge libraries shared and util into one (called common)2021-04-02T10:51:32ZMaxime PerrotinMerge libraries shared and util into one (called common)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/67MSC: When creating a second global comment, the first one is deleted2021-04-02T10:51:32ZMaxime PerrotinMSC: When creating a second global comment, the first one is deletedhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/68MSC editor crash using ASN messages2021-04-02T10:51:30ZMaxime PerrotinMSC editor crash using ASN messages1. launch the editor
2. Select ASN1 file (use the one attached) [DataView.asn](/uploads/2df3c7b619f8c98e88846fce3d401b45/DataView.asn)
3. add 2 instances, make an arrow (message) between them -> this will open a dialog. In that dialog...1. launch the editor
2. Select ASN1 file (use the one attached) [DataView.asn](/uploads/2df3c7b619f8c98e88846fce3d401b45/DataView.asn)
3. add 2 instances, make an arrow (message) between them -> this will open a dialog. In that dialog click on this button
![image](/uploads/35698e9d7139b5932565c0b3b976584c/image.png)
4. Create the new message like this ![image](/uploads/a9d3ac2af1cf9c0c7747c0a228b05ec0/image.png)
5. Press OK, then back in the previous dialog select the new msg and click on Copy from Declaration ![image](/uploads/fdda68116275ddae02ed40366a6c49d7/image.png)
6. Double click on the Value to open this dialog:![image](/uploads/635d14ac8086158a459ae2e73cbf0ff1/image.png)
7. Just click on OK, you will get back there: ![image](/uploads/e409b314d0d9a02d5181da15eb1e49dc/image.png)
8. Now double click on the value again to edit it.. -> **It segfaults**https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/69Debian 10 compilation issues2021-04-02T10:51:32ZMaxime PerrotinDebian 10 compilation issuesNinja builds fail the same way as make
![image](/uploads/e1dd49dfe01bb890a1a11cb8912e2ffb/image.png)
And if I run ninja again several times, it fails the same way in different place
From Maxime as well:
It seems not to be very determi...Ninja builds fail the same way as make
![image](/uploads/e1dd49dfe01bb890a1a11cb8912e2ffb/image.png)
And if I run ninja again several times, it fails the same way in different place
From Maxime as well:
It seems not to be very deterministic. Sometimes the build works, sometimes not.
The documentation of cmake suggests that the subprojects that are included using add_subdirectory: https://cmake.org/cmake/help/v3.0/command/add_subdirectory.html?highlight=add_subdirectory should start with a project() statement. There is none in the tst_ projects. Perhaps adding them (e.g. project(tst_chartitem) at the first line of CMakeLists.txt in the relevant subfolder) could help making it more deterministic?https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/70Issue with MSC streaming mode: long message fails the whole update2021-04-02T10:51:30ZMaxime PerrotinIssue with MSC streaming mode: long message fails the whole updateThe streaming mode does not behave properly
when you execute the attached scenario step by step you see that the first message is displayed as expected:
![image](/uploads/3289da471607daa5b9fafd3d8f22e989/image.png)
However the second ...The streaming mode does not behave properly
when you execute the attached scenario step by step you see that the first message is displayed as expected:
![image](/uploads/3289da471607daa5b9fafd3d8f22e989/image.png)
However the second message makes it scroll up unexpectedly (**this is the first problem**)
![image](/uploads/21bdf1cc852e900c426af353b595ad57/image.png)
then if you let the scenario run (adding messages), the messages move **down** (this is the second problem)
![image](/uploads/71ac0ff9532dc126eeb8ebc7b31895fa/image.png)
The drawing expands infinitely instead of keeping max 10 messages with a diagram of a fixed size.
Use the attached test script to reproduce. Place it in `src/applications/msceditor/scripts` (replace the existing one) and run the following:
```
$ msceditor -p 34622 &
$ ./stream.py
```
[astream.json](/uploads/316ac5d29beff82417b98eb0ddc33d75/astream.json)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/71MSC Streaming mode: Position Attribute is ignored for instances2021-04-02T10:51:31ZMaxime PerrotinMSC Streaming mode: Position Attribute is ignored for instancesThe file `remotecontrolhandler.cpp` contains the code handling the commands to control the streaming scene.
The command `Instance` allows to create a new MSC instance on the scene.
In the function `handleInstanceCommand` there seems to...The file `remotecontrolhandler.cpp` contains the code handling the commands to control the streaming scene.
The command `Instance` allows to create a new MSC instance on the scene.
In the function `handleInstanceCommand` there seems to be a attribute named `pos`:
```
const int pos = params.value(QLatin1String("pos"), -1).toInt();
```
However this attribute seems to be ignored, and it is effectively not possible to set the position of the created instance on the scene.
This is needed because by defaults, instances are created too close to each other:
![image](/uploads/21537c48ecd40d3472166d1d64d2e161/image.png)
There are two options:
1. Actually process the `pos` attribute to let user define the x position of the instance on the scene
2. or Set a default distance between instances which allows reasonably long messages to be displayedhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/72MSC Editor: The SAVE option does not save the model2021-04-02T10:51:31ZMaxime PerrotinMSC Editor: The SAVE option does not save the modelIf you create a model and then try to quit the tool, it opens a pop up to warn you and propose to save:
![image](/uploads/d804ebb9d12f02686ceaab01bff8d8b1/image.png)
However, if you press Save, it still quits without saving anything.If you create a model and then try to quit the tool, it opens a pop up to warn you and propose to save:
![image](/uploads/d804ebb9d12f02686ceaab01bff8d8b1/image.png)
However, if you press Save, it still quits without saving anything.https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/73Check Windows CI to avoid hard coded compiler path2021-04-02T10:51:31ZMaxime PerrotinCheck Windows CI to avoid hard coded compiler pathhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/74MSC: Fix and document the remote handler instance POS paramter2021-04-02T10:51:31ZMaxime PerrotinMSC: Fix and document the remote handler instance POS paramterhttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/75MSC: in streaming mode, grow/shrink the window as needed2021-04-02T10:51:32ZMaxime PerrotinMSC: in streaming mode, grow/shrink the window as needed![image](/uploads/189152622a1283fa5b120db50d7d4df6/image.png)
the window should grow according to the number of instances to make sure they are visible, but the window should not waste space on the screen (since it is controlled by anot...![image](/uploads/189152622a1283fa5b120db50d7d4df6/image.png)
the window should grow according to the number of instances to make sure they are visible, but the window should not waste space on the screen (since it is controlled by another application)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/76MSC: Check the text input of all entities (like for the actions)2021-04-02T10:51:31ZMaxime PerrotinMSC: Check the text input of all entities (like for the actions)https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/77Don't have a zip file inside a zip file for the docs artifact2021-04-02T10:51:31ZMaxime PerrotinDon't have a zip file inside a zip file for the docs artifacthttps://gitrepos.estec.esa.int/taste/spacecreator/-/issues/78Run the manual tests at the end of sprint 42021-04-02T10:51:31ZMaxime PerrotinRun the manual tests at the end of sprint 4https://gitrepos.estec.esa.int/taste/spacecreator/-/issues/79Build the MSC plugin2021-04-02T10:51:32ZMaxime PerrotinBuild the MSC plugin