Using RobotBuilder
 

I've been trying to get started with RobotBuilder (exporting to Java), but every time I try there are missing import statements and arguments. It's been very frustrating and I'm wondering if I should just stick to manually writing code myself. I can run through the project and correct the errors, but I'm very concerned about trying to explain this process to any other member of our team (ei those with little to no programming experience). RobotBuilder looks like a great tool, but I'd like it to generate runnable code.

After exporting to eclipse you can go to the classes with errors and click ctrl shift o and it will automatically import.

Sent from my SM-G935R4 using Tapatalk

Re: Using RobotBuilder
 

What classes aren't generating correctly? Subsystems, PID subsystems, ... ?

Re: Using RobotBuilder
 

As I said before, I already fixed the imports, it's just irritating.

Robot.java was the only class with an error other than missing imports, it was trying to create a new DriveBase with no arguments (ei not passing any motors). I think this is because I named a subsystem DriveBase. I've since corrected it. I'll be testing the code on the robot later to day and let you know if any other errors are discovered.

Re: Using RobotBuilder
 

My team started with RobotBuilder last year, and it was a struggle at first. RobotBuilder can't edit the imports because the imports can't be in its auto-generated code blocks. You will have to import them yourself. As for writing the code yourself, both options have their advantages. You can keep your stuff more orderly if you write it yourself, but it's going to take longer.

I know from experience. I've been trying to argue to program in pure Java. I still write my own code in Java. The other programmer writes in robot builder. We cooperate, and we use the one that works best.

Re: Using RobotBuilder
 

If there's something actually buggy you should probably submit an issue here. Also, +1 for just using Java; we spent the first week of the season training people so that we could do that better.