Drop Mech Keys Meetup Recap - Thanks for Visiting!
As you may have seen, we just hosted our first meetup in quite a while here at Drop HQ (Corsair HQ, but they seem to like us enough :) )! It was a blast to get to meet so many enthusiasts local to the bay area—it had been 10 years since I was last hanging out with keyboard nerds in the bay, at KeyCon 2014. We had a great time hosting everyone at the offices, checking out all the very nice boards y'all brought, and sharing some of our own projects/spaces! I knew it would be fun to host in the Game Room when I first saw it in person, but seeing it come to fruition was still so cool. Alright, I'll stop blabbering on now. xD Picture time! (Oh, real quick - there will be more of these! Stay tuned for more info and to catch the next one!)
May 15, 2024
For reference, here is the error I got:
In file included from ../../Macro/PartialMap/macro.c:30:0: ./generatedKeymap.h:226:27: error: ‘KEY_FUN4’ undeclared here (not in a function) Guide_RM( 77 ) = { 1, 14, KEY_FUN4, 0 }; ^ make[2]: *** [CMakeFiles/kiibohd.elf.dir/Macro/PartialMap/macro.c.o] Error 1 make[1]: *** [CMakeFiles/kiibohd.elf.dir/all] Error 2 make: *** [all] Error 2
PartialMaps[1]="mdergo_numpad stdFuncMap"
Apparently, the kll compiler assumes you want access to the function keys only on the defaultMap, so an explicit call to stdFuncMap is unnecessary. For partial maps, it appears the assumption is that you won't be using function keys, so the compiler does not include them automatically.
Also note, this workaround breaks default lcd functionality. The layers will work, but any use of a function key defined on a partialMap will not update the lcd with the layer activated by that key (function keys defined on the defaultMap still work fine with the lcd).