Lazy Brown Dog introduced a new method of input, a cluster of keys which would likely never be pressed in normal operation, and impossible on some keyboards, was implemented which would trigger a macro in AutoHotKey. AutoHotKey has the advantage of easily discerning which program is activated to determine the appropriate macro and macros can be written more easily than rewriting and uploading the to keyboard hardware. For now, AHK only pops up a text window indicating that the input was recognized.
Another new addition was the feature of pseudo-random number generation in the form of virtual dice. D4 through D1000 is accessible from eight different buttons,, and the buttons below them roll the equivalent die and press <enter> immediately after. This was also the source of some confusion when I thought the keyboard was in Numpad mode, but unpredictable numbers kept appearing when pressing the same key.
With the first layer sorted out, moving to the next layers revealed the lights were not displaying correctly. Since I did not know what layer I was on, it was hard to know what keys I should expect. The code from the previous keyboard did not work since the old keyboard had two layers and this has four. After the color changing issues were worked out, the colors were also expanded so that a wider variety of colors were available.
Exciting color changes were on my list of desired improvements, so I kept moving in this vein. Previously, when the layer changed, the colors would snap to the desired color as quickly as possible, which will remain the default but I created a list of animations I wanted to be able to switch between, and the first was to fade from the current color to the new layer's color.
The next animation I wanted was to change the LEDs one at a time. A lot of scaffolding code for the color fading was useful for this animation style, so it did not take as long as the first.
Another animation I wanted was to flash pseudo-random colors, then come to rest on the new layer's color. For some reason, that code did not work well and rather than fuss with it, I scrapped it all and moved to the next animation which was to turn off the LEDs sequentially, and then turn them back on, in the color of the new layer.
The rest of the summary posts 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 and 24HourEngineer.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.
Macros accepted by AutoHotKey
Another new addition was the feature of pseudo-random number generation in the form of virtual dice. D4 through D1000 is accessible from eight different buttons,, and the buttons below them roll the equivalent die and press <enter> immediately after. This was also the source of some confusion when I thought the keyboard was in Numpad mode, but unpredictable numbers kept appearing when pressing the same key.
Results of keyboard dice
With the first layer sorted out, moving to the next layers revealed the lights were not displaying correctly. Since I did not know what layer I was on, it was hard to know what keys I should expect. The code from the previous keyboard did not work since the old keyboard had two layers and this has four. After the color changing issues were worked out, the colors were also expanded so that a wider variety of colors were available.
Expanded spectrum of colors
Exciting color changes were on my list of desired improvements, so I kept moving in this vein. Previously, when the layer changed, the colors would snap to the desired color as quickly as possible, which will remain the default but I created a list of animations I wanted to be able to switch between, and the first was to fade from the current color to the new layer's color.
Gentle fading between layers
The next animation I wanted was to change the LEDs one at a time. A lot of scaffolding code for the color fading was useful for this animation style, so it did not take as long as the first.
Sequential lights for layer changes
Another animation I wanted was to flash pseudo-random colors, then come to rest on the new layer's color. For some reason, that code did not work well and rather than fuss with it, I scrapped it all and moved to the next animation which was to turn off the LEDs sequentially, and then turn them back on, in the color of the new layer.
Changes in color with bouncing animation
The rest of the summary posts 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 and 24HourEngineer.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.
Comments
Post a Comment