Lifx-control-panel

Latest version: v1.8.0

Safety actively analyzes 687918 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 5

1.8.0

* Can now discover all LIFX products and control them using the Lights interface
* Custom Interfaces coming soon...
* Checks product list for Kelvin range and adjusts UI ranges accordingly

EDIT: Fixed crash on start. Binaries have been updated

1.7.6

* Pyinstaller 3.6 fixes several security vulnerabilities
* Updated other key repositories, increasing security and speed

Roadmap:

* i18n and localization

1.7.5

Not secure
Not an essential release; more of a test. Trying to get `README.md` to be the "long description" of the library. Also version should be managed more coherently (single-source of truth).

Because PyPI is so aggressive with their naming policy, I think I'm going to have to reach mach speed on my minor-version numbering system, as each small updated will require a full release, rename, etc. I realize this is to encourage only submitting when you're done. But I really can't add the README to the page without recompiling, uploading, linking, etc.? 😕

1.7.4

Not secure
No functional changes should happen.

Software will now be installed through `pip`.

1.7.3beta1

* Added a Dominant Color feature, similar to Avg. Color except it takes the _mode_ instead of the average. This provides crisper colors, less prone to the "mixed Playdough effect" where everything is some shade of brown.

* Added a Brightness Offset Slider under Settings. This sets a minimum value for brightness during any of the Color Tracking functions (Avg, Dominant, Music). Once again, this provides more saturated colors, and provides a baseline luminance for the lightbulb

The elephant in the room is the size of the exe, which is nearly double. I'm aware of the problem; it's most likely because `numpy` was added as a requirement to get the color value while staying in real-time. This is partly why I made this release a beta, as I want to try and shrink the exe as much as I can. I wanted to provide the executable to anyone interested, as all the features work as intended.

1.7.2

No real functionality changes with this release, although there may be some latent stability increases as a result of some of the refactors. Most notably, all `global` variables have been excised from the codebase! This will make the code a lot more predictable as well as readable.

Also, I've switched to a fresh Python virtual-environment for this build, to make sure the newest modules are installed and nothing weird/gunky has gotten into the build process.

The point of releasing this is mainly to tackle the "False Positive" issue I've been having with some virus scanners. Windows Defender will probably continue to remove it, most likely because the code isn't "signed" by a verified source (which costs a decent amount of money). I do "self-sign" my code, which you can verify by Right-Clicking on the `.exe` file, selecting "Properties", then tabbing to the "Digital Signatures" section. "Sawyer McLane" should be listed as the name of the signer. Through this process, you can at least verify that the binaries are coming from me, and not some 3rd party.

Page 1 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.