wireless
Here are 662 public repositories matching this topic...
-
Updated
May 4, 2022 - Shell
Feature Description
Add the ability to display the grid that blocks snap to in GRC. This should be toggleable and saved using a preference and have a menu item in the dropdown menu to enable/disable.
Feature Urgency
low (just an idea)
More Information
Thanks to @skoslowski for outlining the steps to implement the drawing of the grid:
To implement it, you'll want to start here
-
Updated
Apr 18, 2020 - Python
-
Updated
May 6, 2022 - C++
-
Updated
Aug 26, 2020 - Java
-
Updated
Nov 3, 2019 - Python
-
Updated
Mar 17, 2022 - Python
This is regarding this page:
https://zmk.dev/docs/development/build-flash
If you follow the instructions there, west build re-compiles most code (even if it hasn't been changed) on each build leading to a very long build time.
But you can dramatically reduce it by doing an initial build with all the extra parameters like:
west build -d build/sofle/left -b nice_nano_v2 -- -DSHIELD=sofl
-
Updated
Mar 27, 2022 - Go
-
Updated
Apr 23, 2019 - Python
Indicator CC V4 adds two new commands:
- Indicator Description Get Command
- Indicator Description Report Command
TODOs:
- Implement the new commands
- Implement a
getDescriptionmethod onIndicatorCCAPI - update
@implementedVersiondecor
-
Updated
Oct 13, 2021
Steps to replicate
- Create a VPN server with OpenVPN backend
- Create a template for the VPN server created in step 1
- Create a device and apply the template created in step 2 to this device
- Go to
/admin/pki/cert/and delete the certificate related to the device
Expected Outcome
The certificate is deleted and along with it VpnClient object is also deleted.
**Ac
-
Updated
May 6, 2022 - Python
-
Updated
Apr 25, 2022 - Python
-
Updated
Nov 22, 2019 - Shell
Improve this page
Add a description, image, and links to the wireless topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the wireless topic, visit your repo's landing page and select "manage topics."
A common protocol structure is to have a header containing a
lengthfield, followed by data oflengthbytes, followed by additional protocol fields such as a CRC. If the length field is variable, the position of subsequent URH-specified protocol fields defined by fixed position will not be in the correct location.I do not know the best way to address this, but quick and easy way to support