ZeroDivisionError when Scanner does not specify resolution constraint range step.
-
mariuss
Forgot to attach the log file...
-
onyxfish
- Tag changed from hp to constraint, hp, options, resolution
- State changed from new to duplicate
- Milestone set to 0.5
- Title changed from unhandled exception to ZeroDivisionError when Scanner does not specify resolution constraint range step.
Thanks for the bug report Mariuss. This issue was previously reported as ticket #34 Scanner that does not specify a constraint range step throws inexact values e.... To save you reading that whole thread, a partial fix is currently in the GitHub repository. If you are the type who likes to dig around in source repositories, then you are more than welcome to download and run that version (notes on how to do that are that ticket thread, near the bottom). Otherwise the fix will be in the version 0.5 release.
Thanks again for the ticket. :)
-
mariuss
Thanks for the quick reply, glad to hear that this is a known and fixed issue :-)
Unfortunately I will not be able to test this too soon. Run into this issue with a friend's computer. Next time I am there will try again, hopefully 0.5 will be out by then.
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
