You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For example, suppose a user has a directory with a bunch of text files with names that match Game Objects. This importer would go through that folder and add each text file to an annotation about the Game Object that matches the name of the text file.
This is pretty brittle (changing names of objects would stop the importer from working). We need to discuss this further and think about how it would work.
The text was updated successfully, but these errors were encountered:
Judging by the direction we went with Annotations, I'm not sure address this issue in this way continues to be relevant.
Perhaps more along the lines of what we did with providing guesses for the AssociatedTwineNode editor (see #119) would be eliminate some of the manual work but also keep us from having to create a bunch of restrictions on people's directory structures?
For example, suppose a user has a directory with a bunch of text files with names that match Game Objects. This importer would go through that folder and add each text file to an annotation about the Game Object that matches the name of the text file.
This is pretty brittle (changing names of objects would stop the importer from working). We need to discuss this further and think about how it would work.
The text was updated successfully, but these errors were encountered: