8ae0628ebd
Update travis.yml to point to new bundle repo
6 years ago
13d781214d
Update travis.yml to point to new bundle repo
6 years ago
6d2a3edbd2
Update travis.yml to point to new bundle repo
6 years ago
a0970bf7c8
Update travis.yml to point to new bundle repo
6 years ago
cb081d2b90
Update travis.yml to point to new bundle repo
6 years ago
cac493917b
Update travis.yml to point to new bundle repo
6 years ago
020a67a413
Update travis.yml to point to new bundle repo
6 years ago
b8e10200fa
Update travis.yml to point to new bundle repo
6 years ago
1972c9f7c4
Update travis.yml to point to new bundle repo
6 years ago
2db231da85
Update travis.yml to point to new bundle repo
6 years ago
78816f4b36
Update travis.yml to point to new bundle repo
6 years ago
1c847ac3f5
Update travis.yml to point to new bundle repo
6 years ago
cc26fcc996
Update travis.yml to point to new bundle repo
6 years ago
d3d79760b1
Update travis.yml to point to new bundle repo
6 years ago
d117653f3c
Update travis.yml to point to new bundle repo
6 years ago
21ba3548bc
Update travis.yml to point to new bundle repo
6 years ago
4606191ff6
Update travis.yml to point to new bundle repo
6 years ago
6d3d67157b
Update travis.yml to point to new bundle repo
6 years ago
5e9202d25d
Update travis.yml to point to new bundle repo
6 years ago
3ac5ef6f9c
Update travis.yml to point to new bundle repo
6 years ago
e7e2064e94
Update travis.yml to point to new bundle repo
6 years ago
1bac62e700
Update travis.yml to point to new bundle repo
6 years ago
3d40837e01
Update travis.yml to point to new bundle repo
6 years ago
604f453a8b
Update travis.yml to point to new bundle repo
6 years ago
a855bb83be
Update travis.yml to point to new bundle repo
6 years ago
c7b396e046
Update travis.yml to point to new bundle repo
6 years ago
b9c5fd4c91
Update travis.yml to point to new bundle repo
6 years ago
8605ff7d1d
Update travis.yml to point to new bundle repo
6 years ago
cddb35e172
Update .travis.yml with new bundle pointer
6 years ago
c749214e48
Update README to point to new Kaleidoscope-Bundle-Keyboardio
6 years ago
96cfdd5c65
Merge branch 'master' of https://github.com/keyboardio/Kaleidoscope-LED-Stalker
...
Signed-off-by: matt venn <matt@mattvenn.net>
6 years ago
ab89785ab5
moved to millisAtCycleStart and fixed overflow bug present on ARM platform
6 years ago
869d434362
Merge pull request #4 from BenGardiner/patch-1
...
fix: yellow was cyan
6 years ago
2a3a8341c3
fix: yellow was cyan
...
the 'r' and 'b' values for cyan were swapped.
Signed-off-by: Ben Gardiner <ben.l.gardiner@gmail.com>
6 years ago
c996c5e4e1
Minor code refactoring
...
In the Topsy case, pre-calculate `mapped_key.raw` for both branches, and only
modify its flags in the unishfted branch. This saves us about a dozen bytes of
PROGMEM.
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
6 years ago
2ebf02d76a
Simplify the shift tracking
...
We do not need to track which shift is pressed, so lets use a bool instead of a
bitfield. Makes the shift checking code smaller too!
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
6 years ago
f74292fbee
If a Topsy key is active, consume shifts
...
This allows us to reliably do the `Shift+TOPSY` case.
Fixes #11 .
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
6 years ago
2bfd64a900
Simplify the "shifted" case too
...
Like in the unshifted case, avoid injecting keys, and fiddle with `mapped_key`
instead. This allows us to get rid of the `TOPSYTURVY` bitflag.
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
6 years ago
1e0ac664fe
When seeing a modifier key, don't set last_pressed_position_
...
We do not want modifier keys to abort the TopsyTurvy magic.
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
6 years ago
62f9fe481d
Simplify the normal, "unshifted" case
...
Instead of injecting a new event, modify `mapped_key` instead, and give it a
`SHIFT_HELD` flag.
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
6 years ago
209a92b6e0
If a non-Topsy key toggles on, disable repeating the Topsy one
...
This is to avoid the case where chording a Topsy and a non-Topsy key would
result in both being repeated very fast. This happened because each cycle we
sent two reports: one for the Topsy key, one for the others. This didn't allow
the host's normal repeating behaviour to kick in, and instead, resulted in both
keys being input very fast.
Fixes #5 .
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
6 years ago
8a426cc3e3
Drop the idle-case check
...
We're not calling `onKeyswitchEvent` in the idle cases anymore, drop the check
for a few bytes saved.
Signed-off-by: Gergely Nagy <algernon@keyboard.io>
6 years ago
d931ae1efa
Merge pull request #20 from keyboardio/bug/numlock-sync-report-spam
...
Bug/numlock sync report spam
6 years ago
e3acde9419
rename a variable that didn't match the style guide
...
Signed-off-by: Jesse Vincent <jesse@keyboard.io>
6 years ago
c6886b09fb
Change cleanupDone to numlockUnsynced to better represent what it does
...
Signed-off-by: Jesse Vincent <jesse@keyboard.io>
6 years ago
efbf158b13
Bring back the LED breathing effect
...
Signed-off-by: Jesse Vincent <jesse@keyboard.io>
6 years ago
8fb50b2415
Only run our "toggle numlock mode" once upon toggle of the layer
...
Signed-off-by: Jesse Vincent <jesse@keyboard.io>
6 years ago
79996b7216
Only try to reset the numlock led if we actually haven't done the
...
cleanup
Signed-off-by: Jesse Vincent <jesse@keyboard.io>
6 years ago
7c1a5cea95
Refactoring. no functional changes
...
Signed-off-by: Jesse Vincent <jesse@keyboard.io>
6 years ago
b491146f33
Extract a couple methods and rename a variable
...
Signed-off-by: Jesse Vincent <jesse@keyboard.io>
6 years ago
Jesse Vincent
matt venn
Gergely Nagy
Ben Gardiner
Gergely Nagy
Jesse Vincent