[LTGLambChops]

Thanks Brad for the response!

I'm hoping that this season I'm not seeing too many "else throw new Exception("We can't do that.")" lines of code. Looking through the 2015 library source code it looks like the team was horribly rushed to get past this point. My suggestion is to force the application to change something and, by using a log, teams would be able to see what's going on on the Rio. There are other things that we (current two mentors wanting to add things into the WPILIB) will pull together some projects that we've been coding and will try to see if we can set it up for both C++ and Java, LabVIEW would still take time to figure out.

However; my concerns exist within the WPILIB and, I guess this may the only way to put it but, the prevention of Application closures. Either a logging system that details which file's source code it's coming from or else a way to tell them (the teams) that the system is being changed in order to fix a current system in place. For instance, rather than shutting the application down in PIDwrite for CANTalons it may be easier to give a warning that the system cannot handle specifically requested settings and they will be changed rather than simply shutting the program down. If that doesn't sound likely due to time constraints I'm sure there are a bunch of teams willing to help go through beta code and set those features up.

Thanks, again, for the response Brad!