Unmapped key: Unknown(248)

[leanghok120]

Whenever I run "rustyvibes ~/Downloads/Soundpacks/{switch}" in a terminal (I'm on linux),
After a while it displays "Unmapped key: Unknown(248)", I use cherrymx-brown-abs and nk-cream

[leanghok120]

(This is what running rustyvibes for 5 hours straight looks like)

[InSasquatchCountry]

GPT-4o mini
The errors you're encountering indicate that there are keys being pressed that are not mapped in your keycodes.rs file. The Unknown keys with specific integer values (like 62 or 248) correspond to key codes that are not defined in your code_from_key function.

To resolve this issue, you can do the following:
Identify the Keys: First, you need to identify which keys correspond to those unknown key codes. You can do this by checking the documentation for the rdev library or by logging the key codes when they are pressed.
Add Missing Key Mappings: Once you identify the keys, you can add them to your keycodes.rs file. For example, if you find that key code 62 corresponds to a specific key (like a multimedia key), you can add a constant for it and update the code_from_key function accordingly.
Handle Unknown Keys Gracefully: If you want to handle unknown keys without causing errors, you can modify the code_from_key function to log or ignore unmapped keys instead of just returning None. This way, you can keep track of which keys are being pressed without causing your application to crash.
Here’s an example of how you might modify the code_from_key function to log unknown keys:

pub fn code_from_key(key: Key) -> Option<i32> {
    match key {
        // ... existing mappings ...
        _ => {
            // Log the unknown key code
            println!("Unmapped key: {:?}", key);
            None
        }
    }
}

Testing: After making these changes, test your application again to see if the errors persist. If new unknown keys appear, repeat the process of identifying and mapping them.
If you provide the specific keys that correspond to the unknown key codes, I can help you create the appropriate mappings!

---

On my mac I get an error for the right option/alt key that I have remapped to right control. I was able to identify it by looking at https://github.com/Narsil/rdev/tree/main, but honestly I just minimize the terminal window anyway so I'm not going to bother rebuilding rv.

CONTROL_RIGHT: CGKeyCode = 62;

[InSasquatchCountry]

Whenever I run "rustyvibes ~/Downloads/Soundpacks/{switch}" in a terminal (I'm on linux), After a while it displays "Unmapped key: Unknown(248)", I use cherrymx-brown-abs and nk-cream

I was having the same issue so I used this as an opportunity to fork the project and submit my first real pull request with the behavior of no output by default unless --debug is flagged.

cargo install --git https://github.com/insasquatchcountry/rustyvibes.git --branch feature/silent-mode-default

If you have already installed the original Rustyvibes using cargo install rustyvibes and then run the above, Cargo will replace the existing rustyvibes binary with the version from my fork’s feature/silent-mode-default branch. You should be good to go. ✌️