Core Meta Panel & Gamepiece Configuration

[BrandonPacewic]

• Moved all remaining general and advanced options to be in one tab.
• Everything is now structured like AARD-1685: Joint Config Panel #995 for easy (er) refactoring of ConfigCommand.py.
• Integrated Friction Data Export #1014.
• Made some small improvements to the way auto calculating robot weight works.
  • Now a checkbox instead of a button.
  • Choosing a different unit will now update he value input in real time.
• Also refactored gamepiece config options to be structured like AARD-1685: Joint Config Panel #995.
• Switching between Static and Dynamic export mode will toggle the visibility of the joint config tab, the gampiece config tab, and the dynamic export specific options.

I am still not 100% sure how I feel about structuring the UI in this way. Seems better than what we were doing before but I still think it can be improved upon.

I combined both these JIRA tickets to avoid any downtime in the gamepiece configuration functionality as the meta panel task would have overridden / deprecated some of the field configuration options.

To Test

This is a rather large PR here are somethings to make sure still work:

1. Exporting a robot normally.
2. Exporting a field normally.
3. Selection of game pieces working as expected.

Most of these changes were structural so everything should look and feel like it always has.

Important

Blocked by:

• Friction Data Export #1014.
  • Need to move friction data into the general tab for dynamic exports.
• Refactor: Types/**/* -> Types.py #1045.
  • Types file for unit typing and conversions.

JIRA Issue - Meta Panel
JIRA Issue - Gamepiece Config

[PepperLola]

Everything looks good and works well. Automatically showing/hiding tabs based on static vs dynamic makes the process a lot simpler.

Maybe the auto calculate robot weight checkbox should go above the weight though? It's something the user would need to think about before the weight because changes to it impact whether or not they're able to manually input a weight.

[BrandonPacewic]

Maybe the auto calculate robot weight checkbox should go above the weight though? It's something the user would need to think about before the weight because changes to it impact whether or not they're able to manually input a weight.

I would be open to suggestions, I made it this way because I felt it was weird to separate the other checkboxes but I could be persuaded otherwise.

[PepperLola]

I would be open to suggestions, I made it this way because I felt it was weird to separate the other checkboxes but I could be persuaded otherwise.

Yeah I was considering mentioning that in my reply. I think either way works when you've gone through the process already. The only reason I mention that is because my first instinct after hearing that it was a checkbox was to look above. It didn't take long to find it so I don't think it's super important.

[BrandonPacewic]

Yeah I was considering mentioning that in my reply. I think either way works when you've gone through the process already. The only reason I mention that is because my first instinct after hearing that it was a checkbox was to look above. It didn't take long to find it so I don't think it's super important.

I would have liked to make the checkbox part of the row with the rest of the weight inputs but I had problems making a labeled checkbox. Something I can revisit later on.

[azaleacolburn]

The code quality here is substantially higher than some of the older code in ConfigCommand.py