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
Remaining lifetime (years) does not go negative #6359
Comments
chindit wrote:
This comment was imported from FlySpray: https://bugs.openttd.org/task/6359#comment14041 |
Alberth wrote:
This comment was imported from FlySpray: https://bugs.openttd.org/task/6359#comment14042 |
chindit wrote:
Attachments
This comment was imported from FlySpray: https://bugs.openttd.org/task/6359#comment14043 |
frosch wrote:
This comment was imported from FlySpray: https://bugs.openttd.org/task/6359#comment14044 |
chindit wrote:
This comment was imported from FlySpray: https://bugs.openttd.org/task/6359#comment14045 |
adf88 wrote:
This comment was imported from FlySpray: https://bugs.openttd.org/task/6359#comment14063 |
I do like the: warn if an condition order makes no sense. I also agree that <= 0 should trigger when it becomes 0, not when it becomes slight-less-than 1 (it is also very common to make that exception for your minimum and maximum .. the time between 100% and 99% is often longer/shorter than from 99% to 98%). But negative remaining lifetimes .. that makes no sense to me :D The estimation might be wrong, but I cannot have a negative remaining lifetime. Not even for comparison that makes sense to me :D |
Thanks for this. There's been no activity on this for some time, and as it stands, it doesn't look likely that it will go any further. I'm closing it as we try to keep the issue count low for OpenTTD, it helps us focus on things that are important and fun. Feel free to discuss in irc or request re-opening if you disagree. Thanks for contributing! |
Simons_Mith opened the ticket and wrote:
Reported version: 1.5.1
Operating system: All
This issue was imported from FlySpray: https://bugs.openttd.org/task/6359
The text was updated successfully, but these errors were encountered: