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

Finish Implementing Presets Backend #26

Closed
dv-anomaly opened this issue Jun 6, 2017 · 3 comments
Closed

Finish Implementing Presets Backend #26

dv-anomaly opened this issue Jun 6, 2017 · 3 comments
Assignees

Comments

@dv-anomaly
Copy link
Collaborator

Waiting on UI implementation, most of the backend code is in-place thanks to @tassaron2. Remove button does not currently have a method associated with it.

@tassaron tassaron self-assigned this Jun 8, 2017
@tassaron
Copy link
Collaborator

tassaron commented Jun 14, 2017

All preset functionality should be working as of 2ad14b7. There are methods now for creating, deleting, renaming (saving+deleting), opening, clearing, exporting, and importing presets. Export and import use the same file format as project files (called avl instead of avp) and are used to transfer presets to other systems.

Only feature remaining to add is exporting and importing multiple presets in one avl file. The file format already supports doing this, and presets exported with this version will be forward compatible. So adding it to the backend will be simple, but a GUI dialog for selecting/deselecting presets out of an avl file must be designed.

The preset list must allow selection of multiple presets at once for bulk export and delete functions. Rename function will continue to use a single selection.

@dv-anomaly
Copy link
Collaborator Author

dv-anomaly commented Jun 23, 2017

@tassaron2 @rikai @djfun

Only feature remaining to add is exporting and importing multiple presets in one avl file.

Should we wait on implementing this until after we hit our first milestone? The only other issue is packaging and we are ready for testing.

@tassaron
Copy link
Collaborator

Yes, I agree we can wait to implement multiple preset functionality until a future milestone. At that time we can create a new issue.

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