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

Optimize key selection when using "Write Dump (Clone)" #340

Open
arkdchst opened this issue Feb 23, 2021 · 1 comment
Open

Optimize key selection when using "Write Dump (Clone)" #340

arkdchst opened this issue Feb 23, 2021 · 1 comment
Milestone

Comments

@arkdchst
Copy link

If I want to write dump to tag that has same keys as in dump stored I must wait key mapping process. I can solve it by exporting keys from dump to separated .keys file, but it would be better (?) to automate this process and optionally check keys from dump file first.

Thanks!

@ikarus23
Copy link
Owner

Fair. It is likely that if you do not copy a dump to a new tag (with default keys) you most likely writing it to the original tag. Therefore, using the keys from the dump first (right after the default keys) sounds reasonable.

This should go well together with #43. The approach for the quick dump/mapping features would be to select a dump file instead of a key file.

I'm not sure when I will have the time to implement it, but I add it to the todo list.

@ikarus23 ikarus23 added this to the Todo milestone Feb 24, 2021
@ikarus23 ikarus23 changed the title Optimize write tag Optimize key selection when using "Write Dump (Clone)" May 22, 2021
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

2 participants