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

Add optional built building count to recipe rows v2 #144

Open
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

veger
Copy link
Contributor

@veger veger commented Dec 28, 2021

This PR extends PR #118 by making the check recursive so it shows the error on the top recipe and all subgroups until the actual recipe that has not enough buildings.

Saklad5 and others added 7 commits May 23, 2021 14:53
This variable, which defaults to null, can be used to track the number of buildings that have actually been built. This number has no impact on the model.
Dropdown menu items for setting or clearing the builtBuildings value have been added for each recipe row.

These items mirror the behavior and implementation of those for fixedBuildings, for the most part.
The initial value is buildingCount rounded up, or 0 if buildingCount is negative.
As 0 is a valid value, clearing builtBuildings returns it to null.

Shopping lists now use the builtBuildings value instead of buildingCount if the former is not null.
The text field is only visible if builtBuildings is not null, and is placed under the building count. It is colored grey to indicate that it is not playing a role in the model.
If the number of buildings needed for the model's solution is greater than the specified number of built buildings, the recipe will now be flagged accordingly.
This makes it substantially easier to determine which recipes need to be revisited if a change is made.
To make issues more apparent, the entire page now displays an error message (like with deadlocks) if a recipe needs more machines than it currenty has built.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants