Add initial support for encoders in simulation

[LoadingPleaseWait]

The EncoderJNI class has been added in patches so that encoders can be used in simulation.

[JaciBrunning]

I can only assume this is in reference to #35

I'm going to leave this open for now, but not merged. I won't merge it until some further support is added (e.g. "working"), or until a discussion is made on it.

I think most users would rather Crash in simulation, knowing that the Encoders aren't supported in simulation, than to be reading false values of 0 and ripping their hair out wondering why their PID loops aren't working.

[LoadingPleaseWait]

You are correct; this is for #35. Waiting for further support sounds fair. I'll add a way for the user to change the encoder values through the simulation GUI in another commit for this pull request.

[JaciBrunning]

I'd recommend the GUI for the rate of encoder change as well as value. That would allow for Drive Train PID tuning, as well.

[LoadingPleaseWait]

Alright, I'll have both the rate and the value in the GUI.

[LoadingPleaseWait]

In my most recent commit, I added GuiNumberSpinners for the rate and value of encoders. I also added more GuiNumberSpinners for analog input. I know it's not very pretty since there isn't much space in the window but it gets the job done.

[floogulinc]

@LoadingPleaseWait can you post a screenshot of the GUI changes?

[LoadingPleaseWait]

I know it looks a little different because I'm in Ubuntu.

[floogulinc]

Looks like we still need to fix the margins on the little buttons...

@LoadingPleaseWait does that only show up if you've created an encoder object? Also, how does it handle multiple encoders (and ones of different types)?

Maybe they should be next to the DIO or analog in pins they were created using.

[LoadingPleaseWait]

For now, the encoder label and buttons are there all the time and all encoders have those values.

[floogulinc]

I think we should avoid cluttering up the interface like this and have it work like everything else (DIO, analog IO, talons, PWM) and have encoders only show up when they have been instantiated. Also, users should be able to set individual encoder values instead of setting every encoder.

I also think that we should come up with a plan for how to support the many different sensors wpilib supports. We should also look at support for sensors plugged into Talon SRXs.

[JaciBrunning]

I would recommend putting encoders under a different window, like how SRXs and Pneumatics. Sensors are the hardest thing to simulate, as it relies a lot of user intuition as to what values to put in

[LoadingPleaseWait]

I'll put the encoder count and rate in a window just like the Talon SRXs and Pneumatics. I'll also make it so that you can control each encoder individually.

[LoadingPleaseWait]

I've added a commit which puts the encoders in a different window and you can now control all the encoders individually.

[JaciBrunning]

Looks good. I'll check out the commit and give it a test after Week 3 events (I fly out in about 12 hours). @floogulinc could you give this a test if you get a free moment?

[Samcfuchs]

Hey what's the status on this PR now?