Windows Device Reading and Template selection

[Rexeh]

Problem Naming of templates, and need for them to match device names is causing the main confusion around how to use the tool and why it may not work.

Solution

• On boot the tool will read connected devices, storing them in an internal DB
• Users will now be required to bind a joystick to a template file
• If the device is disconnected then the exporting should still work for users
• Should this fall-back to named templates?

Considerations

• Handling duplicate naming (with distinct GUID)
• Removing stored configurations
• Auto bind devices where 100% match can be assured?
• How to feedback that a device is not configured with a template

[Rexeh]

Integration with directInput done.