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

Pattern registration #678

Merged
merged 14 commits into from
Sep 1, 2024
Merged

Conversation

raoulvdberge
Copy link
Contributor

See #612
See #98

The equals/hashCode must be the ID. Otherwise, multiple exact same patterns
would only occur once in the network pattern set.
And when you remove a pattern at that point,
even if there is another still present,
the pattern would be removed entirely from the
set since it's stored once because it's
the same pattern, even if duplicated.

This also makes it easier to cache the
output resources properly.
…hint

isActive and isHighlightable is checked, to avoid rendering
the background on processing matrix slots
which should be rendered in the scissor
instead.
Use term "autocraftable" instead of "craftable"
everywhere as that makes it more clear
what it means.
It was necessary because the backing list
can never contain zero of a resource,
and because the grid resources used to keep
a reference to the resource amount in the list.
So we needed the zeroed system to properly show
"0" in the gui. However, now we just query the
backing list for the amount, which can be 0.
Copy link

sonarcloud bot commented Sep 1, 2024

@raoulvdberge raoulvdberge merged commit 25666be into develop Sep 1, 2024
6 checks passed
@raoulvdberge raoulvdberge deleted the feat/GH-612/pattern-registration branch September 1, 2024 15:20
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.

1 participant