Add example app showing Mouse, Tablet, Joystick... Data on an ILI9341 display

Thanks mostly to Mike (@mjs513) - a WIP to support some of the digitizer tablets that are not properly supported by Mouse.

Like Wacom Intous...

Did some quick edits, to try this out on my T4. beta

Decided maybe needed top header to mention this currently requires SPIN, ILI9341_t3n libraries, Also thought I would mention which pins, which I made different for T3.6 versis T4.

Also removed the ili9341_due_config.h file as nothing in it was used.

And added a message to the screen saying it was waiting for Joystick object.

Updated joystickbt

Wip2 bluetooth

Turn off Debug (Serial1 and Bluetooth)

Turn off the debug support, so if pulled in to Master other users can use it without needing to setup Serial1

Fixed the order of bytes output when we show a bluetooth address.

Also moved the updated JoystickBT example up one level, such that the new version overwrote the previous version...

Did quick test with PS3...

Update  to the Joystick examples

Wip2 bluetooth - update

Looks like some devices when ask for extended inquriy results instead might return results with RSSI... So needed to process those as well

Updated with additonal axis page

BT - Try extended information on bind query

Trying out using the extended Inquiry data search instead of the real simple one.  This allows us to hopefully get the name of the device as part of this, which now allows the PS4 to know it is a PS4 on the Pair type constructor.

Still WIP to understand XBox one...

Wip2 bluetooth update for xbox

Fix for Battery and LEDS for PS4

Update to joystick and example

Support to pair PS3 if it knows the BTADDR and user presses select and PS button and plugged in USB.

Remembers remote name, and tries to get it when PAIR version of code is running.  (Currently fails).

Does some mapping of PS3 Bluetooth data to match USB HID data.

Warning: as part of debuggigng why joystickType value was changing, I changed the class to make it a function you call instead of just a member variable.  Should mark it inline...  I think I caught all of the places in example code that was accessing it.  If we find we want ability for user probram to update it, should add another member to explicityly set it.

I have some PS3 support working... Hope I did not break PS4.... ;)

Also This assumes that you did a bind of the dongle to PS3 external, no support yet, I did this on RPI3...

Rumble needs work!

Updated Joystick, examples and added sixaxis code

Hopefully did not break other things...

Find that the PS4 requires you to ask to connect versus some/most other devices will do the request...

Also found issue without printing, where adding a delay(1) in a couple of places appears to help when Serial1 printing is not on

Was issues not detecting that ISR bind was asked for, also not special casing when we are doing a bind to know which message to send next....

At least with the Tecknet mouse...

There are issues with binding when already trusted... Need to debug, also likewise if it times out and tries to restore the connection, but at least the beginning is getting some values

I put in hopefully the start of Bluetooth Mouse.

However the one mouse I have is not even trying to talk to the dongle, so not have not seen any data to verify that it is correct and to see the actual data returned...

There are some of the BT dongles that have a device type of 0xff instead of the correct one, so added table of VID:PID to check against, currently only one in list.  If it is this pair the Bluetooth system will claim it.

PS4 starting to work, Still some rumble issues.

Also some WIP parts for caching remote name

Some of these changes also came from @mjs513

Updated wiht my ps4 BT changes

Hopefully not everything screwed up... :D