2017-07-27 18:56:50 +00:00
|
|
|
/* Copyright 2017 Joseph Wasson
|
|
|
|
*
|
|
|
|
* This program is free software: you can redistribute it and/or modify
|
|
|
|
* it under the terms of the GNU General Public License as published by
|
|
|
|
* the Free Software Foundation, either version 2 of the License, or
|
|
|
|
* (at your option) any later version.
|
|
|
|
*
|
|
|
|
* This program is distributed in the hope that it will be useful,
|
|
|
|
* but WITHOUT ANY WARRANTY; without even the implied warranty of
|
|
|
|
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
|
|
|
|
* GNU General Public License for more details.
|
|
|
|
*
|
|
|
|
* You should have received a copy of the GNU General Public License
|
|
|
|
* along with this program. If not, see <http://www.gnu.org/licenses/>.
|
|
|
|
*/
|
|
|
|
#include "process_steno.h"
|
2017-07-26 21:41:39 +00:00
|
|
|
#include "quantum_keycodes.h"
|
2017-08-20 03:23:39 +00:00
|
|
|
#include "eeprom.h"
|
2017-07-26 21:41:39 +00:00
|
|
|
#include "keymap_steno.h"
|
|
|
|
#include "virtser.h"
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
#include <string.h>
|
2017-07-26 21:41:39 +00:00
|
|
|
|
|
|
|
// TxBolt Codes
|
|
|
|
#define TXB_NUL 0
|
|
|
|
#define TXB_S_L 0b00000001
|
|
|
|
#define TXB_T_L 0b00000010
|
|
|
|
#define TXB_K_L 0b00000100
|
|
|
|
#define TXB_P_L 0b00001000
|
|
|
|
#define TXB_W_L 0b00010000
|
|
|
|
#define TXB_H_L 0b00100000
|
|
|
|
#define TXB_R_L 0b01000001
|
|
|
|
#define TXB_A_L 0b01000010
|
|
|
|
#define TXB_O_L 0b01000100
|
|
|
|
#define TXB_STR 0b01001000
|
|
|
|
#define TXB_E_R 0b01010000
|
|
|
|
#define TXB_U_R 0b01100000
|
|
|
|
#define TXB_F_R 0b10000001
|
|
|
|
#define TXB_R_R 0b10000010
|
|
|
|
#define TXB_P_R 0b10000100
|
|
|
|
#define TXB_B_R 0b10001000
|
|
|
|
#define TXB_L_R 0b10010000
|
|
|
|
#define TXB_G_R 0b10100000
|
|
|
|
#define TXB_T_R 0b11000001
|
|
|
|
#define TXB_S_R 0b11000010
|
|
|
|
#define TXB_D_R 0b11000100
|
|
|
|
#define TXB_Z_R 0b11001000
|
|
|
|
#define TXB_NUM 0b11010000
|
|
|
|
|
|
|
|
#define TXB_GRP0 0b00000000
|
|
|
|
#define TXB_GRP1 0b01000000
|
|
|
|
#define TXB_GRP2 0b10000000
|
|
|
|
#define TXB_GRP3 0b11000000
|
|
|
|
#define TXB_GRPMASK 0b11000000
|
|
|
|
|
|
|
|
#define TXB_GET_GROUP(code) ((code & TXB_GRPMASK) >> 6)
|
|
|
|
|
2017-07-27 04:51:41 +00:00
|
|
|
#define BOLT_STATE_SIZE 4
|
|
|
|
#define GEMINI_STATE_SIZE 6
|
2017-08-20 03:23:39 +00:00
|
|
|
#define MAX_STATE_SIZE GEMINI_STATE_SIZE
|
2017-07-27 04:51:41 +00:00
|
|
|
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
static uint8_t state[MAX_STATE_SIZE] = {0};
|
|
|
|
static uint8_t chord[MAX_STATE_SIZE] = {0};
|
|
|
|
static int8_t pressed = 0;
|
|
|
|
static steno_mode_t mode;
|
2017-07-27 04:51:41 +00:00
|
|
|
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
static const uint8_t boltmap[64] PROGMEM = {
|
2017-07-26 21:41:39 +00:00
|
|
|
TXB_NUL, TXB_NUM, TXB_NUM, TXB_NUM, TXB_NUM, TXB_NUM, TXB_NUM,
|
|
|
|
TXB_S_L, TXB_S_L, TXB_T_L, TXB_K_L, TXB_P_L, TXB_W_L, TXB_H_L,
|
|
|
|
TXB_R_L, TXB_A_L, TXB_O_L, TXB_STR, TXB_STR, TXB_NUL, TXB_NUL,
|
|
|
|
TXB_NUL, TXB_STR, TXB_STR, TXB_E_R, TXB_U_R, TXB_F_R, TXB_R_R,
|
|
|
|
TXB_P_R, TXB_B_R, TXB_L_R, TXB_G_R, TXB_T_R, TXB_S_R, TXB_D_R,
|
|
|
|
TXB_NUM, TXB_NUM, TXB_NUM, TXB_NUM, TXB_NUM, TXB_NUM, TXB_Z_R
|
|
|
|
};
|
|
|
|
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
static void steno_clear_state(void) {
|
|
|
|
memset(state, 0, sizeof(state));
|
|
|
|
memset(chord, 0, sizeof(chord));
|
|
|
|
}
|
|
|
|
|
|
|
|
static void send_steno_state(uint8_t size, bool send_empty) {
|
|
|
|
for (uint8_t i = 0; i < size; ++i) {
|
|
|
|
if (chord[i] || send_empty) {
|
|
|
|
virtser_send(chord[i]);
|
|
|
|
}
|
|
|
|
}
|
2017-07-27 04:51:41 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
void steno_init() {
|
|
|
|
if (!eeconfig_is_enabled()) {
|
|
|
|
eeconfig_init();
|
|
|
|
}
|
|
|
|
mode = eeprom_read_byte(EECONFIG_STENOMODE);
|
|
|
|
}
|
|
|
|
|
|
|
|
void steno_set_mode(steno_mode_t new_mode) {
|
|
|
|
steno_clear_state();
|
|
|
|
mode = new_mode;
|
|
|
|
eeprom_update_byte(EECONFIG_STENOMODE, mode);
|
|
|
|
}
|
|
|
|
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
/* override to intercept chords right before they get sent.
|
|
|
|
* return zero to suppress normal sending behavior.
|
|
|
|
*/
|
|
|
|
__attribute__ ((weak))
|
|
|
|
bool send_steno_chord_user(steno_mode_t mode, uint8_t chord[6]) { return true; }
|
|
|
|
|
|
|
|
__attribute__ ((weak))
|
|
|
|
bool postprocess_steno_user(uint16_t keycode, keyrecord_t *record, steno_mode_t mode, uint8_t chord[6], int8_t pressed) { return true; }
|
|
|
|
|
|
|
|
__attribute__ ((weak))
|
|
|
|
bool process_steno_user(uint16_t keycode, keyrecord_t *record) { return true; }
|
|
|
|
|
|
|
|
static void send_steno_chord(void) {
|
|
|
|
if (send_steno_chord_user(mode, chord)) {
|
|
|
|
switch(mode) {
|
|
|
|
case STENO_MODE_BOLT:
|
2019-02-24 03:32:48 +00:00
|
|
|
send_steno_state(BOLT_STATE_SIZE, false);
|
|
|
|
virtser_send(0); // terminating byte
|
|
|
|
break;
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
case STENO_MODE_GEMINI:
|
2019-02-24 03:32:48 +00:00
|
|
|
chord[0] |= 0x80; // Indicate start of packet
|
|
|
|
send_steno_state(GEMINI_STATE_SIZE, true);
|
|
|
|
break;
|
2017-07-26 21:41:39 +00:00
|
|
|
}
|
|
|
|
}
|
2017-07-27 04:51:41 +00:00
|
|
|
steno_clear_state();
|
|
|
|
}
|
|
|
|
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
uint8_t *steno_get_state(void) {
|
|
|
|
return &state[0];
|
2017-07-27 04:51:41 +00:00
|
|
|
}
|
|
|
|
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
uint8_t *steno_get_chord(void) {
|
|
|
|
return &chord[0];
|
2017-07-27 04:51:41 +00:00
|
|
|
}
|
|
|
|
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
static bool update_state_bolt(uint8_t key, bool press) {
|
|
|
|
uint8_t boltcode = pgm_read_byte(boltmap + key);
|
|
|
|
if (press) {
|
|
|
|
state[TXB_GET_GROUP(boltcode)] |= boltcode;
|
|
|
|
chord[TXB_GET_GROUP(boltcode)] |= boltcode;
|
|
|
|
} else {
|
|
|
|
state[TXB_GET_GROUP(boltcode)] &= ~boltcode;
|
|
|
|
}
|
2017-07-27 04:51:41 +00:00
|
|
|
return false;
|
|
|
|
}
|
|
|
|
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
static bool update_state_gemini(uint8_t key, bool press) {
|
|
|
|
int idx = key / 7;
|
|
|
|
uint8_t bit = 1 << (6 - (key % 7));
|
|
|
|
if (press) {
|
|
|
|
state[idx] |= bit;
|
|
|
|
chord[idx] |= bit;
|
|
|
|
} else {
|
|
|
|
state[idx] &= ~bit;
|
|
|
|
}
|
2017-07-27 04:51:41 +00:00
|
|
|
return false;
|
2017-07-26 21:41:39 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
bool process_steno(uint16_t keycode, keyrecord_t *record) {
|
2017-07-27 04:51:41 +00:00
|
|
|
switch (keycode) {
|
|
|
|
case QK_STENO_BOLT:
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
if (!process_steno_user(keycode, record)) {
|
2019-02-24 03:32:48 +00:00
|
|
|
return false;
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
}
|
2017-07-27 04:51:41 +00:00
|
|
|
if (IS_PRESSED(record->event)) {
|
|
|
|
steno_set_mode(STENO_MODE_BOLT);
|
2017-07-26 21:41:39 +00:00
|
|
|
}
|
2017-07-27 04:51:41 +00:00
|
|
|
return false;
|
|
|
|
|
|
|
|
case QK_STENO_GEMINI:
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
if (!process_steno_user(keycode, record)) {
|
2019-02-24 03:32:48 +00:00
|
|
|
return false;
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
}
|
2017-07-27 04:51:41 +00:00
|
|
|
if (IS_PRESSED(record->event)) {
|
|
|
|
steno_set_mode(STENO_MODE_GEMINI);
|
|
|
|
}
|
|
|
|
return false;
|
2017-07-26 21:41:39 +00:00
|
|
|
|
2017-07-27 04:51:41 +00:00
|
|
|
case STN__MIN...STN__MAX:
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
if (!process_steno_user(keycode, record)) {
|
2019-02-24 03:32:48 +00:00
|
|
|
return false;
|
2017-07-27 04:51:41 +00:00
|
|
|
}
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
switch(mode) {
|
2019-02-24 03:32:48 +00:00
|
|
|
case STENO_MODE_BOLT:
|
|
|
|
update_state_bolt(keycode - QK_STENO, IS_PRESSED(record->event));
|
|
|
|
break;
|
|
|
|
case STENO_MODE_GEMINI:
|
|
|
|
update_state_gemini(keycode - QK_STENO, IS_PRESSED(record->event));
|
|
|
|
break;
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
}
|
|
|
|
// allow postprocessing hooks
|
|
|
|
if (postprocess_steno_user(keycode, record, mode, chord, pressed)) {
|
2019-02-24 03:32:48 +00:00
|
|
|
if (IS_PRESSED(record->event)) {
|
|
|
|
++pressed;
|
|
|
|
} else {
|
|
|
|
--pressed;
|
|
|
|
if (pressed <= 0) {
|
|
|
|
pressed = 0;
|
|
|
|
send_steno_chord();
|
|
|
|
}
|
|
|
|
}
|
Improve state/chord handling and clean up namespace
Some values that can never, ever, change were held in local
variables, rather than in PROGMEM. Fixed.
Change "pressed" to a signed int so the test for < 0 makes
sense, and to avoid possible weird failure modes in the
case where a key release comes in when pressed is already
zero. (Shouldn't happen, sure, but computers are weird.)
A lot of things in process_steno had external linkage for no
particular reason. They've been marked static. Stuff still
builds.
Distinguish between currently-held keys and keys that have
been held, and expose these values through a nicely-named API
so other code could, say, check on the current set of steno
chording in order to make displays. Also in passing fix up the
"state" value having external linkage so it could clash with
other people's variable declarations.
The API also provides hooks for key processing and steno chord
events, so you can monitor those events without having to
run in matrix_scan_user and recheck the values directly. Also
document these.
There is no path through processing a key that doesn't
end with a return false, so the nested return foo() are
gone and we just return false.
2017-11-18 15:38:15 +00:00
|
|
|
}
|
|
|
|
return false;
|
2017-07-27 04:51:41 +00:00
|
|
|
}
|
2017-07-26 21:41:39 +00:00
|
|
|
return true;
|
|
|
|
}
|