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
This is currently logged as a Trace error and any file after the first returned from Directory.EnumerateFile() is ignored. The user should be prompted to associate each SET file with a sprite so projects can be merged.
This is only important for databases other than SFRAME, which is all we're working on so far.
The text was updated successfully, but these errors were encountered:
This will allow for an easy way to identify which tables came from the
standard gameset (std.set) and which came from RES files in the DBF
format. This should, eventually, help resolve issues #11, #12 and #37.
We can simply add loaded DataTables to the current ActiveGameSet now and
saving will handle it by verifying the "FileName" propery in the
DataTable's ExtendedProperties collection. This will allow for resolving
issues #11, #12 and #37 once the UI functionality is there.
#11 and #37 are closed but this one will still require some UI work to expose to the user. As it stands now, additional sets (which are just DataSets) are merged to the currently-open set, if any, by default. Obviously, this can be a problem if a standard sprite, like ballista, was edited because now the tables will contain multiple rows for the same sprite.
I'm not sure how granular I'll get with this but I think at least choosing to exclude tables from the merge would be nice.
This is currently logged as a Trace error and any file after the first returned from Directory.EnumerateFile() is ignored. The user should be prompted to associate each SET file with a sprite so projects can be merged.
This is only important for databases other than SFRAME, which is all we're working on so far.
The text was updated successfully, but these errors were encountered: