Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
Maybe this could be solved by making the valign and halign tags work on edges
too? Then we cood choose which side of the line the text is placed on. Default
could be centered in the direction of the arrow.
Original comment by fropet...@gmail.com
on 6 Feb 2015 at 8:03
I tried valign tag - not recognized on arrows
Original comment by glago...@gmail.com
on 6 Feb 2015 at 8:33
I know; I meant it as a suggestion for the devs.
Maybe this is because of text alignment when the same arrow is placed
horizontally; the text is centered along the arrow, but the first line is
placed above it and the rest below. It seems to me that the text block is fixed
vertically relative to the arrow center. This might be in order to avoid text
being _on_ the arrow which would be hard to read. Just a guess.
Still, the horizontal alignment changes from being centered to being placed to
the right side when changing direction, so it should be possible to change the
vertical alignment at the same time.
Enabling the valign/halign tags for this kind of text field would be practical
too, but maybe that should be a separate request?
Original comment by fropet...@gmail.com
on 6 Feb 2015 at 4:46
Great idea!
Original comment by glago...@gmail.com
on 6 Feb 2015 at 4:55
Hi
Thanks for the report, the text should be centered (and will be with the next
release) as you can see in the attached png example
fixed in r1316
Original comment by AFDiaX
on 6 Feb 2015 at 5:56
Attachments:
just a short note to the last comment:
text placement for relations is quite complex and the calculation for
horizontal and vertical lines is different so they do not influence each other
(I guess the horizontal logic with first line of text above, rest below the
relation line is OK)
halign and valign do not work because they would be hard to implement in a way
which always looks good (because of all the combinations of relation-line
alignment, amount of text lines, ...)
Original comment by AFDiaX
on 6 Feb 2015 at 6:02
Original issue reported on code.google.com by
glago...@gmail.com
on 5 Feb 2015 at 8:33Attachments: