- Updated both FuncMaps to use Soft Replace
- Only used for layers, default and base maps are not affected by soft replace (works like a normal replace)

- Includes symbolic names

- Like Function, these are not valid USB codes, but can be used to easily refer a particular key (no possible with exact name)

U"Lock1"  : layerLock( 1 );
U"Latch1" : layerLatch( 1 );

- Including remote reload example configuration

- All colors (except Fanta Orange) have been reduced by 75%

- This makes it easier to define capabilties in any C file

- Required changing the ScanCode node datastructure
- Interconnect Id's must be stored until the end as it's not possible to calculate the max per node ScanCode until after all the assignments are complete
- Should make future additions more straight-forward (that require per ScanCode information to be stored)

- Prevents fall-through
- Cannot be combined with other result capabilities

- Full HID dictionaries for LED, Consumer Control and System Control
- Re-organized parameter passing (will help with future kll spec additions)

USB Codes not supported for trigger combinations/sequences

Merge upstream changes

- These will be added to the KLL Spec 0.4

- Command Line arguments have slightly changed (will require controller git update)
- In preparation for JSON I/O

- Preparing for JSON->kll and kll->JSON compilation modes

- Recent change broke this functionality

- When possible, use the symbolic names for keys in generatedKeymap.h
  e.g. KEY_A instead of 0x04

- Also added some basic usage scenarios

- Name and kll filenames are treated as special variables
- Using the order of the stacks the compilation order can be inferred (useful for debugging)
- Layer names are finally implemented (instead of Layer 1, Layer 2, etc.)

- Adding latest kll git commit rev
- Adding list of changed files since latest git rev
- Adding list of all command line arguments during generation
- Adding generation timestamp
- Updating copyrights

Don't explode into a 20 line stack trace if the kll file is formatted
incorrectly. Instead simply show the error message and exit with an
error code (which will stop the rest of a make command).

A misformatted file is most likely a user error so showing the full
backtrace for debugging is not necessary. The file and line number
should (hopefully) be enough to fix the parsing error.

- Variable support is not complete
- However PartialMap support is basically ready

0x00 is now treated as a special case.

- Layered assignments were lost due to how the cached assignments were replayed
- Replaying each assignment cache after each file is done processing

- To better support RAM/Flash packing adding support for first scan code calculation
- This way if the first scan code is high (e.g. 0x40) RAM is not used for the scan codes without keys assigned

- Some initial work for KLL variables
- Will be used to influence runtime and compiler features of the firmware

- Required to work with Cygwin Python3