Anyway, let’s put a final word to this, I have the feeling the discussion is not going to be more constructive.
@OP : Frustration is understandable, attitude is not. We do try to do things with end-users in mind, and again, on our free time. We dont owe you anything, and we dont have to bear attitude from you. If you like BMS, good, if you want to provide constructive feedback, good, but if all you have to offer is pure critic with sarcasms, then you are not welcome. And anybody who concurs with this analysis is not a “Falconite”, just a well-educated human being. Personally, I’m not committing time to development to read these kind of post, and I’m sure Kolbe does not either.
Does BMS revolve around BMS developpers, as you put it ? Well yes it does. In this forum, and regarding BMS itself, BMS devs are the one in charge. Deal with it.
Now on to keyfiles.
The old keyfile were an accumulation of stuff added as Falcon evolved, so there no logic whatsoever, no naming convention, no way to find where was what. Kolbe did a wonderful work of reorganizing all that, writing docs to understand keyfiles and providing tools to change them less awkwardly than in the UI. And yes, keyboard mapping are different, because it was a work from scratch. Mind you, not every assignment was changed : U is still uncage, 1 through 9 are still views, QWERTY are still comm menus….
So yes, assignements changed and you need to adapt. This is where layout files and docs are useful (again, provided by Kolbe and in your install).
Now as I wrote before, you can either adapt to them, or bring your 4.32 keyfile and check if you dont have any callbacks now deprecated.
Thread closed. I hope I wont have to read the same kind of post from you again.