Started by Phil Beauvoir, August 18, 2014, 11:35:31 AM
Quote from: Jonas Fluhr on September 17, 2014, 08:23:19 AMI dare to throw in another question: Is it a wished or normal behavior that the name of a relation is showed behind its relation? In many cases this makes the name difficult to read (in particular when the relation is drawn horizontally).I would have expected the name 'within' the relation, i.e. the text field is before the relation and the text fields background color corresponds to the background color of the view. Unfortunately, the option to position the name at source or target is not so helpful in these situations.A more sophisticated solution could offer to resize and move the name's text field freely. Resizing would be useful to wrap the text individually and therewith change the needed space.
Quote from: Jean-Baptiste Sarrodie on September 19, 2014, 13:27:25 PMI've just found another bug (maybe related to Phil's patch on bendpoint fix to grid) : the snap position is moving ;-) in fact it seems the grid used is relative to the part of diagram visible (GEF viewpoint ?) and not the diagram itself. To test: create a view, put 2 concepts, add a relation between them, show the grid, create some bendpoints, see how they match (or not) the grid, move the diagram visible area (may require a small window and more elements), create some new bendpoints, see how they match (or not) the grid: you should not be able to realign with previous bendpoints...
Quote from: Phil Beauvoir on September 19, 2014, 15:35:18 PMThis can happen not only with bend-points but also with figures, when the figure is in negative space. There is a 5-pixel border that causes this. I can remove the border to fix it. But the problem will still occur, say, when a connection or figure is located in negative space and you select it. The Selection handles push the grid a few pixels and mess up the grid positioning for snap. I guess allowing negative space wasn't really a good idea!
QuoteI did notice, however that there is an issue properly situating connectors, particularly when symbols are centered vertically. I've noticed this when one elements realizes another. If the two elements are centered vertically, under some circumstances, the arrow of the realization relationship can end up suddenly very far away from the symbol for the realized element. Also, sometime the problem is with the non-pointy end as well. The fix is to jiggle things around a bit. I've also noticed this with used by as well.
QuoteThe other thing that I have noticed is in the documentation. The chapter Importing and Exporting the Model and its Views is labeled Exporting the Model... in the User Guide table of contents. This makes it harder to search for and find when one is looking to find out how to import.