2018-06-12 (Tu) ModuKey

To make it easy to see which keys served which function, and to decide on future modes, a quick sketch was done with all the keys and the proposed second mode. The dark letters on the top were drawn with a pen because they were what was programmed into the keyboard for the normal typing mode. In the lower portion, the keys shown in dark pen indicate that they were unchanged from the first version.

Sketch of second mode

A spreadsheet was created to clearly demarcate the function of each key while in a particular mode. In the spreadsheet, the fields of each mode were color-coded to match the LED color of that mode. This would change if the number of modes changed. Currently, four modes were available, but only three had anything planned for them. The fourth mode will likely become a macro keyboard for browsers or audio editing in Audacity.

All the keys were programmed by going off the spreadsheet template. One button was programmed at a time. First, the action to take when a button was pressed, followed by the action to take when a button was released. In most cases, this was a matter of pressing one button, and later releasing it. In the cases of the macros, such as typing to omega symbol, the Alt button was pressed, all the relevant num pad numbers were pressed, but the Alt button wasn’t released until the physical key was released.

Spreadsheet with color-coded modes

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 in 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.