ahas36 opened a new issue, #19311:
URL: https://github.com/apache/echarts/issues/19311

   ### Version
   
   5.4.1
   
   ### Link to Minimal Reproduction
   
   
https://codesandbox.io/s/echart-graph-arrow-head-scale-issue-k9pkcs?file=/src/index.js
   
   ### Steps to Reproduce
   
   1. Create a graph with nodes and directed edges.
   2. Implement zoom functionality on the graph.
   3. Observe the relative sizes of nodes and edge arrows as the zoom level 
changes.
   
   ### Current Behavior
   
   When zooming in and out on a graph, the nodes scale properly, but the arrows 
on the edges do not. This results in a visual imbalance where the arrows appear 
disproportionately large or small compared to the nodes at different zoom 
levels, leading to a degradation in the readability and aesthetic appeal of the 
graph.
   
   ### Expected Behavior
   
   The expectation is for the arrows on the edges to scale in proportion with 
the nodes, maintaining a consistent and relative size at all zoom levels. This 
would ensure a balanced and visually coherent graph representation, 
irrespective of the zoom.
   
   ### Environment
   
   ```markdown
   - OS:Widnows 10
   - Browser:Chrome Version 119.0.6045.159 (Official Build) (64-bit)
   - Framework:React
   ```
   
   
   ### Any additional comments?
   
   I encountered this issue while working on a data visualization project that 
requires detailed graph representations. The lack of proportional scaling for 
edge arrows in zoomed views poses a significant challenge in maintaining the 
quality and effectiveness of the visualizations.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to