Support for Alternative Layouts
This is a summary of how alternative layouts have been supported by kits such as Colevrak and Homing. It is not a discussion of alt layout performance and development, but if that interests you I highly recommend starting with Pascal Getreuer’s A guide to alt keyboard layouts (why, how, which one?). It’s a concise and comprehensive overview with links to some great sites that go deeper. He also has a separate Links about keyboards page. The Keyboard layouts doc he recommends explains layout goals and metrics in detail, summarizing the alt layouts discussed here as well as more than one hundred others. Sculpted-profile The majority of custom keycap sets are sculpted-profile (Cherry, SA, MT3, KAT, etc. - more on profiles generally here) so let’s start there. Because each row has a unique keycap shape, alt layouts require a unique keycap for each legend that moves off its QWERTY row. At first there were two The Dvorak layout was patented in 1936 by August Dvorak & William L....
Apr 23, 2024
Is this a defect? Would this be fixed with an update or do I have to send my keyboard in?
Also, the CTRL doesn't work with my Pixel 2 as a host (keyboard recognized by Android, but none of the keys work), whereas my basic $60 Nixeus mechanical keyboard (also on Massdrop) does. Will this also be fixed with an update?
As for compatibility with the Pixel 2 itself as a keyboard...*shrug*? I don't know if they ever even thought of that use case, or if any keyboard manufacturer really has, and your Nixeus may be working as a sheer fluke.
Regarding daisy-chaining power, I don't know if that's an ok reason. In such a case it should just not charge or charge slower, not malfunction. I have another keyboard with a severely underpowered hub (100mA), I'll check how that one behaves.
2. I might've phrased this badly, but I didn't mean full-speed or normal charging, just enough voltage to support #1.
We've done the tests with the Galaxy Note 8 and the Pixel 2 and everything should be working.
So if anyone else complains about a similar problem, ask them to check other ports first in case their motherboard's second controller also has such a bug.