2019-01-03 (Th) ModuKey

Some of the last additions to the ModuKey blogs showed a standing desk with three screens with a laptop as the low-center screen. This has been a convenient arrangement, but the screenshots have a lot of blank space. On the upper-left screen, I kept a diagram of all the keycap diagrams for the four different layers. On the bottom screen was the pjrc.com webpage with the recognized names for all the keys I was adding as well as the gaming software I was using to record software macros to make it easy to program each specific key. For the upper-right screen, the most convenient to look at, I kept the Arduino code I was working on.

Writing a macro to replace my existing code with the new key assignments seemed like a better use of my time as opposed to painstakingly replacing each line while referencing the keymap back and forth. It may take more time in the long run, but it has not felt so tedious.

The first two modules were programmed but the hardest part was the front loading where the macro was written, and a pattern was established for adding the rest of the keymaps.

Screenshot, three screens

ModuKey on GitHub

The rest of the posts for this project have been arranged by date.

First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5

Disclaimer for http://24hourengineer.blogspot.com/

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by  Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.