Issue updating an Edge arrows at runtime ( making it bidirectional )

Open
#391 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp
Domain
desktop

Research direction

Start at WPFGraphControl's runtime edge-arrow update path, focusing on ArrowheadAtSource and the ValueChanged -> Invalidate flow. Reproduce changing a singular target arrow to a bidirectional arrow after graph creation. Done means the update works without missing arrow or arrowPath structures, or the runtime limitation is clearly documented.

Written by the indexing model from the issue text.

Description

Hi!
I'm using WPFGraphControl and trying to modify an edge with a singular target arrow to a bidirectionnal one, which would have both source and target Arrow.
I tried modifying its attribute (ArrowheadAtSource), but if this was at None or NonSpecified when the Graph was generated, it lacks some critical structure ( the arrow itself and the arrowPath ).
And modifying its attribute triggers ValueChanged -> Invalidate, which tries to access unexisting value.

Am I using the wrong flow to modify the arrow of an edge ? Is that not doable at runtime ?
Do I need to fully redo the graph for it to work ?

Dominant language
C#
Stars
1.5k
Forks
319
Avg merge
38m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/automatic-graph-layout

All issues in microsoft/automatic-graph-layout

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.