You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exported SVG are using straight line for connection between nodes, the same as preview in Gephi.
Current Behavior
Connections between nodes in exported svg/pdf/png are curved ????
Possible Solution
Notice the d="M 721.904907,-2560.862549 A 1466.726016,1466.726016 0,0 1,2294.601074,-3309.099121", it means a arc, so I use this part of python code modify it to "L" in my local environment
I know that Gephi is a project with Java as the main development language, but unfortunately I don’t know Java, so I can’t directly open a PR to modify the code responsible for export in Gephi.
Steps to Reproduce
Open some thing, such as a .gv file or graphml, what ever.
Choose a layout you like, and run
Export to svg/png/pdf
Context
Gephi auto generated svg export file are using source code like this
Expected Behavior
Exported SVG are using straight line for connection between nodes, the same as preview in Gephi.
Current Behavior
Connections between nodes in exported svg/pdf/png are curved ????
Possible Solution
Notice the
d="M 721.904907,-2560.862549 A 1466.726016,1466.726016 0,0 1,2294.601074,-3309.099121"
, it means a arc, so I use this part of python code modify it to "L" in my local environmentI know that Gephi is a project with Java as the main development language, but unfortunately I don’t know Java, so I can’t directly open a PR to modify the code responsible for export in Gephi.
Steps to Reproduce
Context
Gephi auto generated svg export file are using source code like this
Correct svg source code should be like:
Your Environment
Product Version: Gephi 0.10.1 202301172018
Java: 11.0.17; OpenJDK 64-Bit Server VM 11.0.17+8
系统: Windows 11版本 10.0 运行于amd64上; GBK; zh_CN (gephi)
用户目录: C:\Users\laoshubaby\AppData\Roaming\gephi\0.10
高速缓存目录: C:\Users\laoshubaby\AppData\Local\gephi\Cache\0.10
The text was updated successfully, but these errors were encountered: