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

Cannot open projects with multiple set files #12

Open
sraboy opened this issue Nov 14, 2015 · 2 comments
Open

Cannot open projects with multiple set files #12

sraboy opened this issue Nov 14, 2015 · 2 comments
Assignees
Milestone

Comments

@sraboy
Copy link
Owner

sraboy commented Nov 14, 2015

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.

@sraboy
Copy link
Owner Author

sraboy commented Dec 19, 2015

See #11 and #37. These will likely be resolved simultaneously as they all have roots in the same issue detailed in #37.

sraboy added a commit that referenced this issue Dec 19, 2015
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.
sraboy added a commit that referenced this issue Dec 19, 2015
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.
@sraboy
Copy link
Owner Author

sraboy commented Jan 1, 2016

#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.

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

No branches or pull requests

1 participant