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

Save menu command does nothing when unit is invalid #456

Closed
assaultdoor opened this issue Feb 18, 2020 · 2 comments
Closed

Save menu command does nothing when unit is invalid #456

assaultdoor opened this issue Feb 18, 2020 · 2 comments

Comments

@assaultdoor
Copy link

Using MML 0.47.4 on OS X, when I try to save a unit that MML thinks is invalid (it's sometimes wrong about that), nothing happens. With 0.43.9-RC3 and earlier versions, I would at least get a warning that I was saving an invalid unit. I have to use Save As to save anything MML thinks might be invalid.

Also, under MML 0.47.2, I would sometimes change the Model field of a unit, make a few other changes, and save it only to find that MML had decided to save it with the old Model name, overwriting the previous unit. This didn't happen every time. I'm not sure what triggered it. It would sometimes happen even after I'd made a bunch of other changes to the unit. Save As always worked properly. I haven't seen this pop up on 0.47.4 yet, but I've gotten used to Save As and have rarely used plain old Save since switching to 0.47.4.

@neoancient
Copy link
Member

Are you saying that Save As will always save it, but Save does nothing when the unit is flagged as invalid?

@assaultdoor
Copy link
Author

That's it.

@neoancient neoancient changed the title Issues with saving Save menu command does nothing when unit is invalid Feb 20, 2020
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