Scale9tiled #930
Closed
Scale9tiled #930
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
added 2 commits
July 4, 2014 11:03
This makes sure, that at least one tile remains, even when there is not enough room for 1 full tile.
added 4 commits
July 7, 2014 15:54
Cause the tiling is just a feature of the Scale9Image and not an own component I think having just one screen for demonstration is better.
|
I added same mechanism to the Scale3Images. Also extended the DisplayObjectExplorer a bit to demonstrate the feature. |
|
Closing. Scale3Image and Scale9Image are removed from Feathers because Starling now has those capabilities natively. |
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.
Hi,
I added support to have Scale9Images tile and stretch the center parts instead of just stretching.
You can turn it on by setting isTiled to true.
I also added an example screen to the DisplayObjectExplorer.
This would fix the feature request #634