Seth Schroeder

Can you 1. back up your key maps 2. install the 2.3.0 release from github (you'll have to uninstall the google play version) 3. restore your key maps 4. turn...

Cool, thanks. Your key maps were working in that log since the device descriptor matched the one in the trigger. I'll wait for your 2nd log.

Okay, interesting. Yeah, the device descriptor does change. Do you have any idea why it changes? Does it ever change back to the one stored in the trigger?

Okay, really strange that it always changes the descriptors. Is using "any device" a solution for you? I would prefer to not have to add a UI setting for one...

Yeah, I will add it to the known issues. I will close this now. :)

I will actually implement a proper fix for this. See the developer checklist for what I'm going to do.

Thank you! I'll check this out at some point, hopefully today. It's great that all your code seems to follow the Key Mapper style/architecture. Was it complicated to figure out?...

Thank you for the feedback. 1. They all have to be separate but I'll move all actions to be subclasses of ActionData so you can type `ActionData.` and then get...

Yeah. You can work on it if you want? Commit each small change you make so it's easier for me to modify your changes.

Okay, that's fine. You don't need to write any html. It's purely markdown, which is why I'm using mkdocs. 😄