Is it just me or does Const Long, Sscanf, Eof etc. in camel case feel super wrong?
Also, it's a bit odd to see Breakpoint, Type, Arr, String included as novelty mod legends, yet no Struct, Return, Void, Unsigned or other actual C keywords. A K&R reference somewhere would be nice to see too.
I agree with what others have said about moving the C novelty mods to the base kit and making them the main feature of the set. With the current market, I don't think this set is likely to hit MOQ if it's this split up.
I think the pink accented Enter doesn't look very good next to the accented Shifts. I suggest dropping that key, or swapping it with a green Enter.
I also think you can drop the green-legend `~, \| keys from base, as the difference in legend color between them and the default keys is barely noticeable. Further, Tab and Backspace legends are already green, so again you have the same accent color on two adjacent rows, which isn't great.
Show Image
(https://i.imgur.com/1cmNf64.jpeg)
FYI, some keys in the Basics kit are currently labeled with the wrong rows:
- 1.5u Type, 2u (mislabeled as 1.75u) Breakpoint should be R2;
- 1.5u Break, 1.75u Breakpoint should be R2;
- 1.75u Const Long, 1.75u Continue, 1.25u Type, 1.5u Print should be R3;
- ISO Printf should span rows R2–R3.
Show Image
(https://i.imgur.com/glIu26m.jpeg)
If you don't end up merging the numpad kit into base, you could add a R1 1u = key to it.
You mean Pascal case? Either way, it's not like there's a convention, it's usually up to a team or company's style guide if anything at all. I do agree though that capitalizing functions especially is NOT something you would see in C code.
Why are you the second person that thinks it's camel case :rolleyes: if anything it's Pascal case, but on second thought both of them only even apply to multi-word names, so it's actually neither. Just a strange design choice that I also disagree with for the record
It is camel case, specifically UpperCamelCase (as opposed to lowerCamelCase). I consciously use and prefer those terms over Pascal case (which I haven't used professionally in years, and probably not since uni).
That aside, the casing for (most of) these words isn't really up to convention because they're reserved C keywords or identifiers, so they wouldn't compile unless spelled exactly. However, I guess it's an alright concession to make in order to fit the typical GMK aesthetic. GMK does have lowercase text mods available, though (e.g. GMK Hennessey), so that may be something worth considering for this set:
More
(https://massdrop-s3.imgix.net/product-images/drop-mito-gmk-hennessey-custom-keycap-set/FP/PMu9PSCRSP2ub2soojXP_pc.png)