| Wrong context in cross table cell [message #1236939] |
Tue, 28 January 2014 07:54  |
Eclipse User |
|
|
|
Hi,
I've created a model with a cross table representation where the cells are element based (e.g. a cell might refer to an entity in my model representing an edge from source to destination).
If I select the cell, I would have expected that the properties of the corresponding edge entity are shown in the properties view. However, it shows the properties of the line containing the model element representing the source of the edge. The label, shown in the cell, clearly indicates the edge.
Am I doing something wrong or is some additional effort needed to set the correct context of the elements who's properties are presented? (I tried Sirius 0.9 as delivered with Kepler as the 1.0 beta to be delivered with Luna.)
Greetings,
Wilbert.
|
|
|
| Re: Wrong context in cross table cell [message #1237004 is a reply to message #1236939] |
Tue, 28 January 2014 10:55  |
| Eclipse User |
|
|
|
Le 28/01/2014 13:54, Wilbert Alberts a écrit :
> Hi,
Hi Wilbert
>
> I've created a model with a cross table representation where the cells
> are element based (e.g. a cell might refer to an entity in my model
> representing an edge from source to destination).
>
> If I select the cell, I would have expected that the properties of the
> corresponding edge entity are shown in the properties view. However, it
> shows the properties of the line containing the model element
> representing the source of the edge. The label, shown in the cell,
> clearly indicates the edge.
I understand you have created a column mapping representing the target
of the edge, a line mapping representing the source and an
IntersectionMApping domain based, corresoonding to the edge semantic entity.
>
> Am I doing something wrong or is some additional effort needed to set
> the correct context of the elements who's properties are presented? (I
> tried Sirius 0.9 as delivered with Kepler as the 1.0 beta to be
> delivered with Luna.)
It sounds like a bug. I tried to create a similar Cross Table on Ecore
(line and column to display the classes of a package and an
IntersectionMapping to represent the EReference) and I observed the same
issue.
Could you report a bug on the Eclipse Sirius Bugzilla [1][2] ?
>
> Greetings,
> Wilbert.
>
Thank you for your feedback.
Regards,
Maxime
[1] https://bugs.eclipse.org/bugs/
[2] https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Sirius
|
|
|
|
|
|
| Re: Wrong context in cross table cell [message #1237295 is a reply to message #1237286] |
Wed, 29 January 2014 05:19 |
| Eclipse User |
|
|
|
Le 29/01/2014 10:51, Wilbert Alberts a écrit :
> Hi Maxime,
Hi Wilbert,
>
> If I understand you correctly, your workaround allows me to change the
> distance in the table itself. That is sufficient for the example I
> provided.
This is it.
> However, the real case I'm working at provides much more
> properties (for such connection) that can not be edited that simple in
> the cell directly.
You could add all these "connection" elements as additional semantic
elements of each line: their properties will be added to the properties
view when you select a line. It can be done with the "Associated
alements expression" [1] of the line mapping (Advanced tab). This can be
done for other types of mappings too [2]. Note that this can have
impacts on the default delete behavior.
Another solution could be to create an Edition table to manage the
properties if your "connections".
>
> Thanks anyway for you reply.
>
> Greetings,
> Wilbert.
>
Regards,
Maxime
[1]
http://www.eclipse.org/sirius/doc/specifier/tables/Tables.html#line_mappings
[2]
http://www.eclipse.org/sirius/doc/specifier/diagrams/Diagrams.html#graphical_elements/Tables.html#line_mappings
|
|
|
Powered by
FUDForum. Page generated in 0.06930 seconds
Home