[Plugin] Fix missing invalidation on various plugin api setters for entities #24310
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
The awesome additions of the OpenGL invalidation in #20073 shined some light on various plugin api setters that were not properly invalidating the affected entity. The issues were likely already present in software rendering for much longer, but I wasn't aware of that until recently.
This PR aims to fix that by calling
Invalidate()
in the various setters that could affect what is shown on the screen, and did not yet invalidate the screen for it.To test it, you can for example open the RideVehicleEditor, and try to change a vehicle's colour, type, or variant. On develop, it will update on the window's viewport, but not always on the main viewport. This is easiest noticeable if you spawn lots of trains, enable the "Synchronise" button, en select "All vehicles on all trains" from the target dropdown.
Thank you for your time. 🙂