(01-31-2021, 03:58 AM)iwubcode Wrote: Thanks for your suggestions. I am not sure I want to introduce the style folder layout because it doesn't allow for future enhancements (all the json is at the device level) and looks kinda strange when you have a single texture. It is also a drastic change in terms of spec. I do like its simplicity, though that's less important as I expect most will be using the tool to create these packs. I'm still thinking about it.So I have now worked my way through many textures, and have looked at what really makes sense.
However, I had a similar idea where you mark both an 'emulated key' and a 'host key' with a 'tag'. That tag can be used to denote a "pressed button" for instance. Then we can introduce tag only controls which would allow us to handle the stick icons or other icons that are device specific but lack a specific emulated key.
The X box xontroler requires 25 default textures, this goes so far without problems But then there are the following common problems that are difficult to work around!
In my opinion, for problem 1, the tag function would be the best solution.
For problem 2 the style function would be the best solution, or of course it would also be possible to extend the tag function.
For problem 3, the overlay function would be the best solution.
Additionally, I would be happy about the following improvements,
1 The possibility to use InputSyntax so that it uses the first match. so if i have `button A`&`button B` it uses the texture for button A and if i have `button B`&`button A` it uses the texture for button B.
2 If he has no match he also generates no texture for the button, this would be logical and necessary for the overlay function.
3 The possibility to define the controllers seperatly. this would make it simply clearer and more adaptable.
I know it's a lot but I think it's worth the effort and thank you for your work.