Adding an overridable method BaseNodeViewFactory.getViewType with default implementation returning the tree node level #53
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 method TreeViewAdapter.getItemViewType then uses BaseNodeViewFactory.getViewType instead of always having to return the tree node level.
Then the client code can use something else than the tree node level for selecting the Binder and its layout file.
See also issue 25 when this kind of feature was requested.
#25
Screenshot for a sample app where all items are displayed with the same binder and layout file
![sample_with_geographic_areas_getViewType](https://user-images.githubusercontent.com/1504507/63587186-8dbfa900-c5a3-11e9-95c0-c0ca39503ac0.jpg)
EXCEPT for one specific binder and layout file for Stockholm, i.e. the yellow item in the screenshot below.
Here is the code using the getViewType method in the sample app for the above screnshot:
TomasJohansson@6992917#diff-effcb19dc75b5646f230694a17d35433