Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
Antidoc
Antidoc
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 0
    • Merge Requests 0
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Wovalab
  • open source
  • AntidocAntidoc
  • Issues
  • #78

Closed
Open
Opened Nov 21, 2020 by Cyril GAMBINI@cgambini

Improve representation of 'Request and Reply' / 'Round trips' in graphs

When a request and reply or round trip event links two modules, in the graphs the arrow only shows one direction. So just looking at the graph, one may think that the communication is one-way.

Maybe adding a arrow tail in case of request and reply would help to better understand that the communication is bi-directional. For round trip events, they may be considered as a combination of request and reply + broadcast. So the arrow tail trick would also work for the request and reply part of it ; adding the broadcast arrow would finalize the graph part of it.

Assignee
Assign to
V1.2
Milestone
V1.2 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: wovalab/open-source/labview-doc-generator#78