varun7654 / autobuilder Goto Github PK

• If the point is not visible on the screen the camera should move to make it visible on the screen
• Add ability for points to be selected in the GUI (probably a darker grey box is just rendered in the background)
• Select the point in the pathrenderer

https://github.com/msgpack/msgpack-java

https://github.com/eishay/jvm-serializers/wiki (Benchmarks but probably not accurate for our case)

We can reduce the size of our trajectories by compacting them into arrays.

• Create the settings menu
• Allow changing the team number
• Allow adjusting trajectory constraints
• Allow changing the field image
• Allow setting the origin point on the image
• Allow changing point scale factor

https://github.com/ezylang/EvalEx/

• Show shooter speed (color code based on error)
• Show limelight distance
• Show hood angle

Rendering of the textbox should be cut off like all the other content

https://dev.languagetool.org/java-api

The highlight splits the text into multiple components and wraping can happen at the end of a component (without a space) which causes the text to wrap at unexpected places.

• Hovering over a position of the path should give you information like expected velocity, acceleration, position, etc.
• Hovering over a position of the path should render the bounding box of the robot at that point
• Hovering over a text box in the GUI should tell you what that value represents (x, y, rotation). Also, put the units (meters)

• Add ability to select text
• Add ability to use up/down arrow keys
• Add ability to ability to hold down keys and have them work
• Make clicking on the text work properly (related #4)
• Have text scroll when it goes outside the text box
• Have text be hidden when it extends outside the textbox

Font rendering looks really bad. Make it look better

A workaround is to disable NT when you're not connected to the robot: https://github.com/FRC3476/AutoBuilder/wiki/Set-up-the-GUI#networktables-enabled

https://libgdx.com/news/2021/05/shape-drawer

If multiple robots on the same alliance use AutoBuilder, the teams should be able to import both autonomous routines into one instance of the program, then tweak and re-export them if necessary.

At the very least, this would allow you to check for possible collisions, even if robots need to cross each other's paths. More advanced uses might even make it possible to do things like pass game objects from one robot to another.

• Needs to be able to tell the character that is clicked on by a mouse
• Also properly add line breaks when text wrap is enabled