Add more preferences for controlling the lumens overlay and environmental lighting #3851
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.
Identify the Bug or Feature request
Improves #3817
Description of the Change
Three new preferences are added to improve the experience with the new lumens overlay and environmental lighting:
There is also a minor tweak to handle a case overlooked in the first PR for #3817: a serialized
LightSource
can rarely be missing alightList
, resulting in a NPE when loading a campaign. This case is now handled inLightSource#readResolve()
.Possible Drawbacks
The ever-increasing set of preferences is now even larger.
Documentation Notes
The thickness of the lumens overlay border can be controlled via the Application tab of the Preferences dialog. Setting it to zero will remove the border entirely.
When MapTool starts, the lumens overlay and/or environmental lighting can be shown. These are also controlled via the Application tab of the Preferences dialog.
Release Notes
This change is