Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

14_SD_Keeloq.pm - fixes #643

Merged
merged 3 commits into from
Sep 2, 2019

Conversation

HomeAutoUser
Copy link
Contributor

@HomeAutoUser HomeAutoUser commented Sep 1, 2019

  • Please check if the PR fulfills these requirements
  • Tests for the changes have been added / modified (needed for for bug fixes / features)
  • commandref has been added / updated (needed for bug fixes / features)
  • CHANGED has been updated (needed for bug fixes / features)
  • What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
  • fix, feature
  • What is the current behavior? (You can also link to an open issue here)
  • shade function not work
  • superfluous readings are always retained
  • What is the new behavior (if this is a feature change)?

- added more information to JaroLift buttons
- fix RFD-FHEM#640 Call SD_Keeloq_binsplit_JaroLift only if verbose >=5
- fix shade function fhem/SD_Keeloq#9
my $Channels = AttrVal($name, "Channels", "");
return "ERROR: you can use Channels = $attrValue only with defined attribut addGroups!" if ($attrValue == 0 && $addGroups eq "");
if ($Channels > $attrValue) {
foreach my $d (sort keys %{$hash->{READINGS}}) {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ist das sortieren notwendig?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In der Sache nicht unbedingt. Es wäre ein klassischer Copy&Paste wie dies da hinkam :-)

Würde das zusätzliche sort so viel ausmachen an Ressourcen? Ja es wäre unötige aber rein informell mal.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Es verbraucht halt CPU Ressourcen weil die komplette Liste sortiert wird.
Wenn man es nicht braucht, sollte man es weglassen

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Es ist doch schon geschehen :-) Somit ist nur das benötigte im Code.

- remove unnecessary sort function RFD-FHEM#643 (review)
sidey79
sidey79 previously approved these changes Sep 1, 2019
@coveralls
Copy link

coveralls commented Sep 1, 2019

Pull Request Test Coverage Report for Build 1721

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at ?%

Totals Coverage Status
Change from base Build 1720: 0.0%
Covered Lines:
Relevant Lines: 0

💛 - Coveralls

@HomeAutoUser HomeAutoUser requested a review from sidey79 September 1, 2019 19:49
@HomeAutoUser HomeAutoUser merged commit a6f28f0 into RFD-FHEM:dev-r34 Sep 2, 2019
@HomeAutoUser HomeAutoUser deleted the dev-r34_Keeloq_fix branch September 3, 2019 15:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants