-
-
Notifications
You must be signed in to change notification settings - Fork 40.4k
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.
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
Add support for "The Ave." keyboard #10042
Conversation
-___- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As its 2 physically different PCBs, it should be split into 2 sub revisions keyboards/kingly_keys/ave/staggered
and keyboards/kingly_keys/ave/ortho
.
That was the original plan. I wasn't sure on exactly if that was the right idea cause they are two different PCBs...but they use the exact same pin-outs, config and mapping. It could have been a single PCB but I don't like swiss cheese PCBs lol. |
@zvecr How do I structure the split? Two different keyboard folders or staggered subfolder (keymap, json, info, and config) within the main? |
Future revisions/sales of the pcb might actually be just combined (staggered and ortho) onto the single pcb |
look into pancake pro micro and pancake BLE those might help you understand to make different versions |
@zvecr Do I still need the initial |
Since the two variations are widely different I would treat them as 2 separate keyboards and leave the root folder empty |
Alright. Removed the the two unnecessary files. :) |
Co-authored-by: Joel Challis <git@zvecr.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GitHub tip: You can apply multiple suggestions to a single commit by using the Files Changed tab.
Co-authored-by: James Young <18669334+noroadsleft@users.noreply.github.com>
Co-authored-by: James Young <18669334+noroadsleft@users.noreply.github.com>
Yeah I think every PR I have open has had some issue with the Tapping term specifically. It was working perfectly before the PR with the same Rev split into two keymaps of Ortho/staggered. Travis doesn’t seem to have an issue with the build strangely enough. |
Yeah I did notice that. I would try building yourself anyway, but maybe it's just me. I could definitely |
I feel like this isn't correct... |
Yep, rules.mk is missing from the |
Do I need one in the parent board directories too? Or should i just duplicate and move the rules.mk from the master parent to the sub directories? There is one for each default Keymap currently |
Yeah, Take
|
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Thanks! |
* Add configurator support for "The Ave." keyboard * Update readme.md * update misc nomenclature * add punctuation * fix miss-placed "0" * update README.md * del. duplicate "F11" in visual layout information * Split PCB configurations into subfolders * update layer template to new matrix title * rm primary <keyboard>.c / <keyboard>.h files * add new end line to both .h subfolder fiels * Apply suggestions from code review * tested update to RGB code * update rgb code * Apply suggestions from code review * Apply suggestions from code review * Apply suggestions from code review * Update rules.mk * Update rules.mk * Delete rules.mk * Delete rules.mk * Update rules.mk * Update config.h * Update config.h * Update keymap.c * Update ortho.c * Update ortho.h * Update config.h * Update keymap.c * Update staggered.c * Update staggered.h * Apply suggestions from code review * Update config.h * Update keymap.c * move and duplicate rules.mk file * Update keyboards/kingly_keys/ave/readme.md * Update config.h * Update keyboards/kingly_keys/ave/config.h
This PR#10042 has a build error, but it has been merged. Why? |
The build failure is not really anything to do with this keyboard's code itself - it's complaining that It should be moved somewhere both action_tapping.c and quantum.h can see it. Maybe action.h? |
workaround: diff --git a/keyboards/kingly_keys/ave/post_config.h b/keyboards/kingly_keys/ave/post_config.h
new file mode 100644
index 000000000..9a69b420f
--- /dev/null
+++ b/keyboards/kingly_keys/ave/post_config.h
@@ -0,0 +1,4 @@
+#ifndef TAPPING_TERM
+# define TAPPING_TERM 200
+#endif
+ |
I have a fix coming for this. That should help detect when tapping term is incorrectly set, either the tapping term itself or the functions. Which is mostly... just adding |
Description
Types of Changes
Issues Fixed or Closed by This PR
Checklist