Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Device: [e.g. OnePlus 6T]
Android version: [e.g. Android 10]
Additional context
Add any other context about the problem here.
I compiled this project and found an issue. This module Android: id="@+id/fab" should be after Android: id="@+id/appBar", otherwise fab will not be visible and cannot be clicked to save. The affected UI controls include fragment_comfig_key_cevent.xml, fragment_pick_coordinate.xml,fragment_pinch_pick_coordinates.xml,fragment_swipe_pick_coordinates.xml。 This software is really great, it perfectly solves the mapping of my car's infotainment button functions, very convenient and practical!
Developer TODO (don't remove)
Discord message link/email recipient
Describe the bug A clear and concise description of what the bug is.
To Reproduce Steps to reproduce the behavior:
Upload a backup of your keymaps. Follow the guide here
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Smartphone (please complete the following information):
Additional context Add any other context about the problem here.
I compiled this project and found an issue. This module Android: id="@+id/fab" should be after Android: id="@+id/appBar", otherwise fab will not be visible and cannot be clicked to save. The affected UI controls include fragment_comfig_key_cevent.xml, fragment_pick_coordinate.xml,fragment_pinch_pick_coordinates.xml,fragment_swipe_pick_coordinates.xml。 This software is really great, it perfectly solves the mapping of my car's infotainment button functions, very convenient and practical!