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.

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

Sidebar not showing all network tables entries #127

Closed
blaine141 opened this issue Jan 13, 2024 · 4 comments
Closed

Sidebar not showing all network tables entries #127

blaine141 opened this issue Jan 13, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@blaine141
Copy link

Describe the bug
I can not get 3d poses to show up on the left when following the "3D Field" tutorial.

To Reproduce
Steps to reproduce the behavior:
Follow the instructions listed in 3D Field to publish Pose3d objects. Both the array and single Pose 3D. They will not show up on the sidebar to select

Expected behavior
The NetworkTables entries appear on the left

Screenshots
Network Tables entries
image

No corresponding sidebar entries.
image

Version (required):
image

Additional context
Maybe it is related to the struct type? I have a Field2d showing up correctly. I am also running from a simulator

@blaine141 blaine141 added the bug Something isn't working label Jan 13, 2024
@jwbonner
Copy link
Member

Are you publishing the fields without a leading /? In the latest released version a leading slash is required for NT entries, though I just pushed a fix for that (12afa31). It's definitely misleading that the examples in the docs don't include that.

Let me know if that seems to explain the issue, otherwise I can do some more digging.

@blaine141
Copy link
Author

Dude!!!! It worked!!! I was reverse engineering your code and using the developer console debugger. I would have never found that.

Is the leading slash a NT standard? If so I can make a PR for the docs.

@jwbonner
Copy link
Member

The leading slash isn't required by NT, so the fix I pushed should make it work properly without that. That should take care of the issue with the docs, but thanks for the offer.

@blaine141
Copy link
Author

BTW, this tool is amazing! This is the best-designed solution I have ever seen introduced into FRC. I really hope everyone starts using this tool so we can see some cool auton and less bugs!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants