wireless
Here are 506 public repositories matching this topic...
-
Updated
Apr 18, 2020 - Python
-
Updated
Sep 29, 2020 - Shell
unicode_literals
was necessary pre-Python 2.6; absolute_import
pre-2.5.
It's especially not necessary on Py3.
Hence in the sence of cleaning up the source tree, deletion of all from __future__ import something
from the python files is desirable. This should ideally not happen manually, but with a script, or command line: we need to do that on master
, but it might also be desirable to
-
Updated
Sep 30, 2020 - C++
-
Updated
Aug 26, 2020 - Java
-
Updated
Nov 3, 2019 - Python
-
Updated
Apr 23, 2019 - Python
Whenever we long press on the tile ( notification panel > share files) it takes to the app settings ( system settings).
I think it would be more useful if it take us to the app itself.
Hope you understood and thank you for the app!
Fix statement condition on "Install custom OpenWISP 2 Python packages" task in pip.yml:
TASK [openwisp.openwisp2 : Install custom OpenWISP 2 Python packages] **********
[DEPRECATION WARNING]: evaluating 'openwisp2_python_packages' as a bare
variable, this behaviour will go away and you might need to add |bool to the
expression in the future. Also see CONDITIONAL_BARE_VARS configur
Move clone-template-form.css to the directory where other similar static files are stored for consistency (the related admin class which calls this file must be updated as well).
-
Updated
Sep 17, 2020 - Python
-
Updated
Nov 3, 2019 - Python
-
Updated
Nov 22, 2019 - Shell
-
Updated
Aug 9, 2020
-
Updated
Sep 29, 2020 - C++
-
Updated
Sep 16, 2020 - Python
-
Updated
Sep 5, 2020 - Python
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
length
field, followed by data oflength
bytes, 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