XInput and HID - architecture

[Juan Jose Gonzalez]

On 03/03/2016 05:30 PM, Henri Verbeet wrote:
> On 3 March 2016 at 16:10, Juan Jose Gonzalez <juanj.gh at gmail.com> wrote:
>> There's still the problem with where to put the
>> serialization/deserialization code. While xinput itself only needs to
>> read the mappings, the config tool needs to be able to read, alter and
>> write them, so we need to at least make the deserialization logic
>> accessible to both modules. Especially for a text serializer, that is
>> definitely not something we would want to duplicate.
>>
> It's probably one of those things where it depends on how the actual
> code is going to look in the end, but if it's simple enough you could
> perhaps implement it as inline functions in some header under
> include/wine/.
I had though about that, but I think its going to be quite a bit of
code. We need to access the correct registry keys, iterate over their
values and sub-keys, and parse each item. It would feel like a big hack
to put all that in a header.