Sample of using build info to generate keystrokes (#412)
* More documentation * Saving crontab for user on host * Restructuring in keeping with recent changes to conventions * Simplify submitting my fave cbbrowne keystroke by using SEND_STRING() * Local change, not apropos to have in this repo * Simplify logic; no need to return so much * Add in a version key * Add docs * Split build date into a separate DEFINE * Ensure there is a value even if not working within a git repo * Should not include the compiled code in the repo * compiled.hex files should not be included in the repo; they represent generated compiled code * Fix spelling in comment * Remove more generated files * Add rule to ignore contents of .build directories; their contents are generated * Revert removals of compiled files
This commit is contained in:
		
							parent
							
								
									91b469d88f
								
							
						
					
					
						commit
						2cf26915e3
					
				
					 6 changed files with 1595 additions and 1603 deletions
				
			
		| 
						 | 
				
			
			@ -28,7 +28,8 @@ doing sundry experimentation:
 | 
			
		|||
     to use it, but hey, it shows how others might use this facility
 | 
			
		||||
     in a more useful context.
 | 
			
		||||
   - Key [2][2] aka "a" uses a random number generator to select a digit 0-9 at random
 | 
			
		||||
   - Key [3][2] aka "z" uses a random number generator to select a letter a-z at random	 
 | 
			
		||||
   - Key [3][2] aka "z" uses a random number generator to select a letter a-z at random
 | 
			
		||||
   - Key [1][3] aka "e" spits out the keymap version number
 | 
			
		||||
 | 
			
		||||
2. Some code structure ideas
 | 
			
		||||
---------------------------------------------------
 | 
			
		||||
| 
						 | 
				
			
			
 | 
			
		|||
		Loading…
	
	Add table
		Add a link
		
	
		Reference in a new issue