eclipse-plugins/edu.wpi.first.wpilib.plugins.cpp/resources/templates/command-based/PIDSubsystem.h

#ifndef $classname_H
#define $classname_H

#include "Commands/PIDSubsystem.h"
#include "WPILib.h"

class $classname: public PIDSubsystem
{
public:
	$classname();
	double ReturnPIDInput();
	void UsePIDOutput(double output);
	void InitDefaultCommand();
};

#endif
Initial checkin of unified hierarchy of WPILib 2015 2013-12-15 18:30:16 -05:00			`#ifndef $classname_H`
			`#define $classname_H`

			`#include "Commands/PIDSubsystem.h"`
			`#include "WPILib.h"`

Version 4 Image Updated the HAL library to work with the new version 3 headers from NI. There were multiple changes in this verison: more PWM generators were added, so the functions for setting PWM signals have been updated. UserWatchdog has been removed, and Watchdog has been removed from WPILib to accomodate for this. Digital selection has been consolidated to one function in the NI headers, so this has been updated in the HAL. New SPI and I2C libraries have been added, but need to be implemented in the HAL before they will work. 2014-02-25 18:43:40 -05:00			`class $classname: public PIDSubsystem`
			`{`
			`public:`
Initial checkin of unified hierarchy of WPILib 2015 2013-12-15 18:30:16 -05:00			`$classname();`
Revert changes preventing old user code from compiling. I'm not 100% sure whether we want these, but they are a quick find and replace to do. Basically, there are two primary things that we have done this summer that break existing user code: -Changing GetInstance() calls to return references instead of pointers. This forces users to change from doing something like LiveWindow::GetInstance()->AddSensor() to LiveWindow::GetInstance().AddSensor(). -Making PIDGet() and related calls const, forcing users to change the function signatures wherever they override them. The GetInstance() calls don't really matter to me either way, especially since there are no real ownership issues going on there, unlike the rest of the smart pointer-related changes. For the const stuff, it is certainly more correct to mandate that user PIDGet() functions be const and the such, but at the same time, I'm not sure that there is any strong need for it, and the errors generated are not the most helpful. While this wouldn't necessarily be an issue for more experienced teams or completely new teams (who don't have any old code to be reusing), it may cause issues for more average teams who aren't familiar with the intricacies of C++ anything. Change-Id: I6e7007982069292ea70e6d0fc8ca40203340df1b 2015-07-24 19:19:40 -04:00			`double ReturnPIDInput();`
Initial checkin of unified hierarchy of WPILib 2015 2013-12-15 18:30:16 -05:00			`void UsePIDOutput(double output);`
			`void InitDefaultCommand();`
			`};`

			`#endif`