Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add Software Bus Structures Reference Diagram to Doxygen Users Guide #212

Closed
skliper opened this issue Sep 30, 2019 · 4 comments
Closed

Add Software Bus Structures Reference Diagram to Doxygen Users Guide #212

skliper opened this issue Sep 30, 2019 · 4 comments
Assignees
@skliper
Labels
invalid

Comments

@skliper
Copy link
Contributor

skliper commented Sep 30, 2019

The attached SB structures reference diagram should be made available in the user's guide.
@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Imported from trac issue 181. Created by sstrege on 2017-03-01T14:25:08, last modified: 2019-07-03T12:48:08

@skliper skliper added this to the 6.7.1 milestone Sep 30, 2019
@skliper skliper self-assigned this Sep 30, 2019
@skliper skliper added the bug label Sep 30, 2019
@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by sstrege on 2017-11-17 14:13:37:

Diagram needs to be updated to include expanded APID name space structures

@skliper
Copy link
Contributor Author

skliper commented Sep 30, 2019

Trac comment by jhageman on 2019-07-03 12:48:08:

Moved unfinished 6.6.1 issues to next minor release

@skliper skliper removed their assignment Sep 30, 2019
@skliper skliper modified the milestones: 6.7.1, 6.7.0, 6.8.0 Sep 30, 2019
@skliper skliper removed this from the 6.8.0 milestone Nov 4, 2019
@skliper skliper added enhancement and removed bug labels Nov 4, 2019
@skliper skliper self-assigned this Feb 26, 2020
@skliper skliper mentioned this issue Mar 3, 2020
Closed
@skliper
Copy link
Contributor Author

skliper commented Mar 12, 2020

Found the png, and part of SB's purpose is to abstract the actual packet format... This level of detail isn't applicable to the API (the available structures and APIs are already documented).
SB structures

@skliper skliper closed this as completed Mar 12, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@skliper skliper

Labels
invalid
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@skliper