Tmx 1.10 #803
Merged
Tmx 1.10 #803
Conversation
This file contains 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
We don't want to expose all the Tiled specific stuff like `editorsettings` on the LITIENGINE API but still the serialization layer should keep the information. #464
- Support repeat properties for image layers. - Support double values for layer offset - Support parallax factors for layers - Support tintcolor property for layers - Add test for image layers Fixes #462
Also apply some minor code improvements. #462
We don't want to expose all the Tiled specific stuff like `editorsettings` on the LITIENGINE API but still the serialization layer should keep the information. #464
- Support repeat properties for image layers. - Support double values for layer offset - Support parallax factors for layers - Support tintcolor property for layers - Add test for image layers Fixes #462
Also apply some minor code improvements. #462
We don't want to expose all the Tiled specific stuff like `editorsettings` on the LITIENGINE API but still the serialization layer should keep the information. #464
- Support repeat properties for image layers. - Support double values for layer offset - Support parallax factors for layers - Support tintcolor property for layers - Add test for image layers Fixes #462
Also apply some minor code improvements. #462
- Support repeat properties for image layers. - Support double values for layer offset - Support parallax factors for layers - Support tintcolor property for layers - Add test for image layers Fixes #462
Also apply some minor code improvements. #462
We don't want to expose all the Tiled specific stuff like `editorsettings` on the LITIENGINE API but still the serialization layer should keep the information. #464
- Support repeat properties for image layers. - Support double values for layer offset - Support parallax factors for layers - Support tintcolor property for layers - Add test for image layers Fixes #462
Also apply some minor code improvements. #462
- Support repeat properties for image layers. - Support double values for layer offset - Support parallax factors for layers - Support tintcolor property for layers - Add test for image layers Fixes #462
Also apply some minor code improvements. #462
- Support repeat properties for image layers. - Support double values for layer offset - Support parallax factors for layers - Support tintcolor property for layers - Add test for image layers Fixes #462
Also apply some minor code improvements. #462
- Support repeat properties for image layers. - Support double values for layer offset - Support parallax factors for layers - Support tintcolor property for layers - Add test for image layers Fixes #462
Also apply some minor code improvements. #462
- Cleanup implementation and add some tests #468
Also remove unnecessary API surface to access custom property type. #468
To retrieve custom property values, there are three options: 1. Get the value and expect it to be there - this will throw if no property with the specified name is present 2. Get the property and define a default which will be returned if it is not present 3. Check via hasCustomProperty first and then retrieve the property. #468
# Conflicts: # litiengine/src/main/java/de/gurkenlabs/litiengine/environment/tilemap/MapRenderer.java # utiliti/src/main/java/de/gurkenlabs/utiliti/renderers/MapObjectsRenderer.java # utiliti/src/main/java/de/gurkenlabs/utiliti/swing/dialogs/MapPropertyPanel.java # utiliti/src/main/java/de/gurkenlabs/utiliti/swing/panels/LightSourcePanel.java
Some minor code cleanup. #803
- Reimplement tile terrain support against the Wang implementation (We no longer support the deprecated Tiled terrain which was deprecated with Tiled 1.5) - Some of the newly introduced properties are just mapped to ensure compatibility when serializing (e.g. objectalignment, fillmode, ...). These settings are not supported by the engine but are kept for informational purposes. Fixes #465
Fix some style issues Fixes #465
No need to throw because most features should still work. It's enough to log a warning. Fixes #456
|
The specification has been updated. The following implementations need to be done separately to take advantage of the now available information.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
No description provided.