GeoRefImage: fix min shutter filter #3133
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also, drive-by fix of `dropend` being ignored
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It seems that the Min Shutter field was intended to filter out all messages with too short of a shutter, but as written, it only removes the shortest one (also, there's a mix of using
minshutterand a hard-coded0.5). I have instead changed it to a loop to remove all instances.Additionally, I noticed that
dropendgot commented out, and uncommented it. I'm not sure why that was done, but it seems mistaken. Please confirm that there wasn't some really good reason for commenting that out.