Login
Register
Feature Requests
Questions
Unanswered
Tags
Ask a Question
yEd Home page
Welcome to yEd Q&A!
Here you can ask
questions
and receive answers from other members of the community and yEd developers. And you can tell us your most wanted
feature requests
.
Most popular tags
import
node
export
labels
edge
nodes
bug-report
layout
excel
groups
graphml
yed
properties-mapper
edges
palette
svg
automatic-layout
swimlane
custom-properties
text
properties
error-report
pdf
group
linux
hierarchical-layout
macosx
bug
label
html
bpmn
kb
print
installation
uml
settings
family-tree
resize
color
label-placement
ui
grouping
url
yed-live
graphmlviewer
line
windows
import-excel
entity-relationship
printing
java
gedcom
background
save
arrow
flowchart
link
image
select
error
license
positioning
structure-view
font
open
icon
lines
data
search
default
arrows
tree
copy
size
graph
64-bit
diagram
neighborhood-view
feature
fit-node-to-label
description
paste
font-size
icons
xml
symbols
alignment
tooltip
custom
shape
move
selection
editing
edit
-
file-format
ubuntu
word
visio
user-defined-symbols
Categories
All categories
Feature Requests
(700)
Help
(2.9k)
Finished Features
(30)
Put Content text of NodeLabel and EdgeLabel to a new line
0
votes
When diff two graphml files, the actual content text of NodeLabel and Edgelabel is at far end of the line, but this should be the most important part of the node. Can you put the text to a new line? I think It's much more user friendly.
text
newline
diff
asked
May 21, 2013
in
Feature Requests
by
anonymous
Your comment on this question:
Your name to display (optional):
Email me at this address if a comment is added after mine:
Email me if a comment is added after mine
Privacy: Your email address will only be used for sending these notifications.
Anti-spam verification:
To avoid this verification in future, please
log in
or
register
.
Your answer
Your name to display (optional):
Email me at this address if my answer is selected or commented on:
Email me if my answer is selected or commented on
Privacy: Your email address will only be used for sending these notifications.
Anti-spam verification:
To avoid this verification in future, please
log in
or
register
.
1
Answer
0
votes
We are aware of the fact that the structure of label data in GraphML is not optimal. Unfortunately, changing said structure would lead to compatibility issues which is why we decided not to do that.
answered
May 21, 2013
by
thomas.behr
[yWorks]
(
161k
points)
Your comment on this answer:
Your name to display (optional):
Email me at this address if a comment is added after mine:
Email me if a comment is added after mine
Privacy: Your email address will only be used for sending these notifications.
Anti-spam verification:
To avoid this verification in future, please
log in
or
register
.
Legal Disclosure
|
Privacy Policy
...