One of the cool things about TreeView is it's ability to support generics e.g.
TreeView<FileSystemInfo> fileTree = new TreeView<FileSystemInfo>();
TreeView<GameObject> tree = new TreeView<GameObject>();
I want to tackle this over the holiday period. At first I was worrying about the fact that the T type is arbitrary and likely tied to user code. Then I realized we can just parse the Roslyn code tree to find the names of the T classes and (if it's not a standard Type) declare our own completely empty ones pre compilation (i.e. at Open time)
e.g.
// Just declare each of the users classes ourselves in memory
class GameObject
{
}
One of the cool things about TreeView is it's ability to support generics e.g.
I want to tackle this over the holiday period. At first I was worrying about the fact that the T type is arbitrary and likely tied to user code. Then I realized we can just parse the Roslyn code tree to find the names of the T classes and (if it's not a standard Type) declare our own completely empty ones pre compilation (i.e. at Open time)
e.g.