Currently, setting the maximum on a logistic request to "inf" does not actually behave as if the request has a maximum of infinity. Rather, it behaves as if there is no maximum set. The difference is relevant when Trash Unrequested is enabled, as a request from N to inf will auto trash anything over N, when logically it should disable trashing for that item (because trashing occurs when the amount in the inventory is greater than the maximum).
So my suggestion is that a new "none" value should be added and used as the default maximum when creating a new logistic request. Dragging the slider all the way to the right should still result in a value of "inf," which should be changed to disable trashing in all cases as you would expect it to.
Logistic requests - "inf" behaves as "none" rather than infinity
Moderator: ickputzdirwech
-
- Fast Inserter
- Posts: 121
- Joined: Sat Nov 09, 2024 2:36 pm
- Contact:
Re: Logistic requests - "inf" behaves as "none" rather than infinity
So your "none" would differ from 0?
I think the default maximum should just equal the minimum, and make inf the same as 2^31-1 (or is it 2^32 - 1?)
I think the default maximum should just equal the minimum, and make inf the same as 2^31-1 (or is it 2^32 - 1?)
Re: Logistic requests - "inf" behaves as "none" rather than infinity
"None" would work exactly the way "inf" currently works, which is that if Trash Unrequested is disabled the item is never trashed, and if it's enabled anything above the minimum is trashed.
"Inf" being the same as 2^32 - 1 is how it should work, but it currently doesn't work that way if Trash Unrequested is enabled.
"Inf" being the same as 2^32 - 1 is how it should work, but it currently doesn't work that way if Trash Unrequested is enabled.
-
- Fast Inserter
- Posts: 121
- Joined: Sat Nov 09, 2024 2:36 pm
- Contact:
Re: Logistic requests - "inf" behaves as "none" rather than infinity
Sorry, I meant people will fet confused between "none" and 0.nzer wrote: ↑Thu Nov 21, 2024 10:56 pm "None" would work exactly the way "inf" currently works, which is that if Trash Unrequested is disabled the item is never trashed, and if it's enabled anything above the minimum is trashed.
"Inf" being the same as 2^32 - 1 is how it should work, but it currently doesn't work that way if Trash Unrequested is enabled.
Also is there a use case where you would want "none" instead of setting the maximum to equal the minimum?
Re: Logistic requests - "inf" behaves as "none" rather than infinity
I mean, it's for the maximum. I don't think people will get confused between "maximum of 0" and "no maximum."IsaacOscar wrote: ↑Thu Nov 21, 2024 11:16 pmSorry, I meant people will fet confused between "none" and 0.
Also is there a use case where you would want "none" instead of setting the maximum to equal the minimum?
And from reading other threads about this, a lot of people apparently like that they can use Trash Unrequested as an on demand "trash down to minimum" button. I don't really get it, but to each their own.