Fixes #138
Many types of nodes were not being included in the output directory detection when using parse files.
What was the solution? (How)
Updated the mappings list for which nodes are detected as having output paths
Refactored the asset management related functionality out into a new assets.py file.
What is the impact of this change?
Hopefully a majority of cases should now be covered by the output directory detection
How was this change tested?
Created a scene file with all of the newly added node types within. Clicked Parse Files and verified that the directories specified in each nodes output paths were included. For testing the Fetch and Wedge nodes I made longer chains with valid output nodes at the end of the chains to ensure they were recursively being checked until finding the end node.
Was this change documented?
No
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
What was the problem/requirement? (What/Why)
Fixes #138 Many types of nodes were not being included in the output directory detection when using parse files.
What was the solution? (How)
assets.pyfile.What is the impact of this change?
Hopefully a majority of cases should now be covered by the output directory detection
How was this change tested?
Created a scene file with all of the newly added node types within. Clicked
Parse Filesand verified that the directories specified in each nodes output paths were included. For testing the Fetch and Wedge nodes I made longer chains with valid output nodes at the end of the chains to ensure they were recursively being checked until finding the end node.Was this change documented?
No
Is this a breaking change?
No
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.