-
Notifications
You must be signed in to change notification settings - Fork 223
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
Screen object unification. #3446
Conversation
367b02c
to
f0dea94
Compare
Tested and ready to go. |
9faa31d
to
3a1f25d
Compare
3a1f25d
to
79a4bac
Compare
I just have a slight comment/request. Maybe that feature could be built-in the base screen object? So you could just toggle it on the elements you want to go disabled when they can't be used? |
Sorry, that's out of scope for this. |
That's all good! |
07b8c32
to
cadf871
Compare
cadf871
to
ff37729
Compare
ff37729
to
a048c13
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Partial review, hasn't made any progress in the past few weeks so I'll probably give the rest of the PR a cursory look-over and then approve.
Description of changes
Why and what will this PR improve
Screen object code is a mess and this cleans it up significantly. Will help a lot with the eventual HUD datum rewrite I have in the pipeline.
Testing
Authorship
Myself.
Changelog
Nothing player-facing.