| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
* Add files via upload
* [keyboard]
* [Keyboard]
* Delete flash_spi.c
* Delete flash_spi.h
* Delete wb32_spi_master.c
* Delete wb32_spi_master.h
* [Keyboard]
* Resolved requested changes
* Resolved requested changes
* Changed rules.mk file accordingly.
* Resolved changes accordingly.
* Update config.h file and rules.mk file
* Removed eeprom_flash.c file
* Update default/keymap.c file
* Delete keyboards/darkproject/kd83a_bfg_edition directory
* Add keyboard
* Add keyboard
* Delete darkproject/kd83a_bfg_edition directory
* Resolved Changes
* Resolved requested changes
* keyboard
* Add keyboard
* Delete keyboard
* Add keyboard
* Delete keyboards/darkproject/kd87a_bfg_edition directory
* update keymap.c file
* update via/keymap.c, config.h and kd83a_bfg_edition.c files
* Delete keymap.c
* Update via/keymap.c, config.h and kd83a_bfg_edition.c files
* update config.h file
* update keymap.c file
* update keymap.c file
* update config.h
* update kd83a_bfg_edition.c
* Resolved requested changes.
* Delete folder which was added accidentally.
* Update keyboards/darkproject/kd83a_bfg_edition/config.h
* Update keyboards/darkproject/kd83a_bfg_edition/keymaps/via/keymap.c
* Update keyboards/darkproject/kd83a_bfg_edition/keymaps/via/keymap.c
* Update keyboards/darkproject/kd83a_bfg_edition/keymaps/via/keymap.c
* Update keyboards/darkproject/kd83a_bfg_edition/keymaps/via/keymap.c
* Update keyboards/darkproject/kd83a_bfg_edition/info.json
* Update keyboards/darkproject/kd83a_bfg_edition/rules.mk
* Update keyboards/darkproject/kd83a_bfg_edition/info.json
* update info.json file
* update config.h file
* Updated requested changes
* update readme.md
* Resolved requested changes
* Update info.json file
* Delete kd83a_bfg_edition.h
* Delete readme.md in default folder
* Update info.json file
* update info.json
* Updated changes
* Updated changes
* Resolved requested changes
* Resolved requested changes
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There was an import cycle in the Python modules:
- `qmk.build_targets` imported `qmk.cli.generate.compilation_database`;
- importing `qmk.cli.generate.compilation_database` requires
initializing `qmk.cli` first;
- the initialization of `qmk.cli` imported the modules for all CLI
commands;
- `qmk.cli.compile` imported `qmk.build_targets`.
This cycle did not matter in most cases, because `qmk.cli` was imported
first, and in that case importing `qmk.cli.generate.compilation_database`
did not trigger the initialization of `qmk.cli` again. However, there was
one corner case when `qmk.bulld_targets` was getting imported first:
- The `qmk find` command uses the `multiprocessing` module.
- The `multiprocessing` module uses the `spawn` start method on macOS
and Windows.
- When the `spawn` method is used, the child processes initialize
without any Python modules loaded, and the required modules are loaded
on demand by the `pickle` module when receiving the serialized objects
from the main process.
The result was that the `qmk find` command did not work properly on macOS
(and probably Windows too); it reported exceptions like this:
ImportError: cannot import name 'KeyboardKeymapBuildTarget' from partially initialized module 'qmk.build_targets' (most likely due to a circular import)
Moving the offending `qmk.cli.generate.compilation_database` import into
the method which actually uses it fixes the problem.
|
|
|
|
|
|
|
|
When multiple `-f FILTER` options were specified, `qmk find` did not
return anything at all instead of printing the list of entries that
matched all of the specified filters.
The problem was that the statement in `_filter_keymap_targets()` that
filled `targets` had a wrong indent and therefore was executed for every
filter instead of only once after applying all filters, and
`valid_keymaps` was actually an iterator and therefore could be used
only once. Moving the statement outside of the loop fixes the problem.
|
|
|
|
|
|
|
|
Co-authored-by: Less/Rikki <86894501+lesshonor@users.noreply.github.com>
Co-authored-by: Duncan Sutherland <dunk2k_2000@hotmail.com>
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Duncan Sutherland <dunk2k_2000@hotmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: jack <0x6A73@pm.me>
|
|
|
|
This reverts commit de3c42125b661f62757f8ee4f6184c089340d3a0.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Remove requirement for `keymap_steno.h` include in keymaps
* Add back keymap_steno.h with a note for the time being
|
|
|
|
|
|
* [Keyboard] Change default implementation for get_layer_name_user
Will now show the layer number instead of "Unknown", since this is
what will be shown if QMK Configurator is used to compile the
firmware.
* [Keyboard] Update the layout info
This makes it look sort of like a macropad + gamepad rather than an 4x6
ortholinear keyboard.
* [Keyboard] Fix default implementation of get_layer_name_user
Based on feedback from code review the implementation was swapped in
favor of using get_u8_str. This implied a change to the argument type
from int to uint8_t, which cascaded into the existing keymaps. (This
made sense in general, since the return type of get_highest_layer is
also a uint8_t.)
|
|
|
|
* fix `layouts` data
* add EoF
|
|
|
|
Co-authored-by: Drashna Jaelre <drashna@live.com>
Co-authored-by: Joel Challis <git@zvecr.com>
Co-authored-by: Ryan <fauxpark@gmail.com>
Co-authored-by: James Young <18669334+noroadsleft@users.noreply.github.com>
|
|
|
|
|
|
|
