|
Re: PIDCommand Java Object life cycle
Thanks for the reply and the correct java terms "heap". My questions are to lean better practice and not form bad habits with the team. I was going to suggest we look at removing the command layers to get to what we want as you suggested. The purpose of the layers was to make this dynamic to respond to vision goal traking. We could set the setpiont in the initialize () and maybe update in the execute ().
The required duplicates are likely from hashing out different atempts. It also my answer why we seen some prints from our end () method before execution.
We will clean things up and test to see where it ends up. Do you have a suggestion to how we would make this dynamic like when we use a setPointCommand to control a PIDSubsytem? Maybe we shouldn't?
|