Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Curious why the graphs are not derived from UDataAsset but rather UObject ? #7

Open
jswigart opened this issue Aug 4, 2020 · 1 comment

Comments

@jswigart
Copy link

jswigart commented Aug 4, 2020

Quick question. I'm curious why the graphs are UObject and not UDataAsset derived?

jinyuliao pushed a commit that referenced this issue May 15, 2021
@BirdCatcherGames
Copy link

This would be pretty helpful. A backwards compatible approach I've found is to create a UPrimaryDataAsset which references the UObject derived UGenericGraph as a TSoftObjectPtr, and override PostEditChangeProperty in UPrimaryDataAssets to traverse the graph and read values (or rarely, make writes to the graph but this brittle). This approach allows for integration with AssetRegistrySearchable UPROPERTYs and loading the graphs on-demand instead of needing the hard link and always keeping them in memory.

If there's any appetite for it, I can make a pr with a UGenericGraphPrimaryDataAsset

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants