Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only send debug info if keycode is mouse related #11

Merged
merged 2 commits into from
Jul 7, 2022
Merged

Only send debug info if keycode is mouse related #11

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ef75a4b
Only send debug info if keycode is mouse related
drashna Jul 7, 2022
cede071
Apply suggestion because drashna is too lazy to open in git locally
drashna Jul 7, 2022
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion keyboards/bastardkb/charybdis/charybdis.c
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -316,8 +316,10 @@ bool process_record_kb(uint16_t keycode, keyrecord_t* record) {
pointing_device_send();
}
# endif // !MOUSEKEY_ENABLE
if ((keycode >= POINTER_DEFAULT_DPI_FORWARD && keycode < CHARYBDIS_SAFE_RANGE) || IS_MOUSEKEY(keycode)) {
debug_charybdis_config_to_console(&g_charybdis_config);
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you also need to gate that with #ifndef NO_CHARYBDIS_KEYCODES.

drashna marked this conversation as resolved.
Show resolved Hide resolved
# endif // POINTING_DEVICE_ENABLE
debug_charybdis_config_to_console(&g_charybdis_config);
return true;
}

Expand Down