| How to save the value of a checkbox? (Sirius Specifier) [message #1852293] |
Mon, 09 May 2022 05:12  |
Eclipse User |
|
|
|
Hello,
I added 2-3 checkboxes to my object in my model (a Capella object for instance):
- Fully Decomposed
- Functions described
- Functions described 2
(Check the Image)
__
When trying to describe the behaviour happening when clicking one of the checkboxes, I am trying three methods:
1) Using SET
2) using LET
3) Using Both.
With "Set", i need an already existing feature to be able to set a new value in something (a feature).
--> Is it NECESSARY to create a new Feature in order to be able to save a checkbox value?
When i insert a random feature name as a value in the SET, clicking on the checkbox would do nothing (the checkbox is not checked).
With "Let", clicking on the checkbox make the checkbox "CHECKED", but as soon as i leave the object properties page, the initial value of the checkbox (uncheked) goes back to normal. It is not saved.
--> My experience with AQL showed me that "let" let you create temporary variables, so I figured the variable is deleted as soon as I am clicking elsewhere.
I figured i should create a variable "LET" then try to save it somehow with "SET"
However, i don't have any corresponding existing feature to store it.
--> Is it NECESSARY to create a new Feature in order to be able to save a checkbox value?
If so, how could that be done with a Sirius Specifier?
[Updated on: Mon, 09 May 2022 06:08] by Moderator |
|
|
|
|
| Re: How to save the value of a checkbox? (Sirius Specifier) [message #1852459 is a reply to message #1852448] |
Tue, 17 May 2022 04:18  |
| Eclipse User |
|
|
|
Hello,
Thanks for your answer!
Yes indeed, it is what I started to figure out little by little, an actual attribute had to be made.
However i Hoped that SIRIUS specifier would be able to allow making with features such as "LET" or create instance, (let being temporaty it does not work, and create instance is not available in the property view description)
___
Yes PVMT can do it, but it cannot be automated, an attribute has to be made manually for each capella element of interest. I would have prefered to automate that.
I am still working on it, and exploring other options.
This forum is so populated but very little people sample participate it is so strange, i thank you for your answer.
|
|
|
Powered by
FUDForum. Page generated in 0.02924 seconds
Home