-
Notifications
You must be signed in to change notification settings - Fork 396
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
TAStudio export to bk2: specify name #4172
Comments
It does not. The current behavior will bring up the save file chooser menu if said bk2 already exists, allowing you to rename it (or just spam enter to overwrite the file regardless). |
I can't even use TAStudio in 2.10.0 right now. I get a configuration corruption issue (nothing to do with #4172, I promise 😭) But in 2.9.1, it asks me if I want to overwrite the existing file, and if I click No, it's the same as hitting cancel. No file picker. |
Old tasprojs are not compatible with 2.10 (they are not expected to be cross version compatible in the first place). You can attempt to migrate them with an exported bk2.
This was added in 2.10, not 2.9.1. |
If that's the case, could you add some kind of version check instead of letting it trip over the config parsing?
|
I can at least confirm the behavior requested in this issue on 2.10. It's a bit odd that the default behavior is to not ask you the name, then if the expected file exists, show a file picker without warning. I would expect it to always show the file picker now. But, I can live with it :) |
Agreed. I've been finding silent export weird since day one, just not annoying enough to go and fix it. Does anyone know why it's still preferred to be silent if it's a new file? |
Summary
The export to bk2 option always outputs a file of the same name as the .tasproj. I'd like to be able to save a particular branch or progress update without overwriting the bk2 for my project. To that end, I'd like an "Export As..." menu item that lets me choose the destination file.
Evidently you touched on this topic in #3504, but it never made it into a feature request.
Host env
The text was updated successfully, but these errors were encountered: