Dynamic NT metadata / plugin can alter tiles and new nt metadata fields #769
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added it as a readable field in NT metadata
implemented a listener singleton for tiles to subscribe to allow plugins to format the gui added dynamic tile content, size, pose and opacity through network tables
Widget display type still only works once per widget
added api listeners to tiles so plugins can alter gui
widget context menu
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Adds more allowed metadata fields to NT for Opacity and ContentVisibility and allows widgets to dynamically update to any new metadata. this is achieved by having an object in API that tiles subscribe/listen to that can change content visibility, opacity, size, position, and widget type. This will allow not just NT but any plugin to have this ability. Tiles now have a lock|unlock option in their context menu that makes them immune to any plugins dynamic changes and in preferences/settings for the NT plugin u can disable the dynamic metadata feature in case it hinders you.
I was having build errors directly pulled off main with examples folder and a file check in build.gradle so if you merge I would recommend throwing out those changes (I'm sorry for the inconvenience) and I will write unit tests soon.
Screenshots