Fixed value of visible and locked attributes on object layers #5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The TMX format uses 1/0 instead of true/false. Tile layers and image layers were already using 1/0.
Author
|
I made this change by editing the file on GitHub so it hasn't been tested in any way. Also, I guess this change might cause compatibility issues with existing exported maps? Currently behavior for "true"/"false" is that Tiled will silently fail to parse the integer and use the default state (visible, unlocked) for all object groups. This issue was found when somebody tried to load an exported map using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The TMX format uses 1/0 instead of true/false.
Tile layers and image layers were already using 1/0.