#158 closed defect (worksforme)
Opened file prompts for save after no changes
Reported by: | ibboard | Owned by: | ibboard |
---|---|---|---|
Priority: | trivial | Milestone: | WarFoundry 0.1 |
Component: | WarFoundry-GUI-WinForms | Version: | |
Keywords: | save load prompt | Cc: | |
Blocked By: | Blocking: |
Description
The "do we need to save" check is supposed to return false if an army has been opened and not edited, but Snowblizz is reporting that opening a file and then closing the army prompts to save it when no changes have been made.
Change History (8)
comment:1 Changed 10 years ago by
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:2 Changed 10 years ago by
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
comment:3 Changed 10 years ago by
Owner: | set to ibboard |
---|---|
Status: | reopened → needinfo |
comment:4 Changed 10 years ago by
Resolution: | → worksforme |
---|---|
Status: | needinfo → closed |
Snowblizz reports that it isn't reproducible. Presumably some change had been made but was forgotten, giving the impression that unchanged army prompted for saving.
comment:5 Changed 10 years ago by
Resolution: | worksforme |
---|---|
Status: | closed → reopened |
Managed to re-create the issue while testing #176. May be a bug or may be because of an earlier exception putting the app in a bad state.
comment:6 Changed 10 years ago by
Resolution: | → worksforme |
---|---|
Status: | reopened → closed |
Rebuild with r279 to stop the exception occurring seems to have stopped the problem occurring. Assuming it is related to other errors, since FrmMain_ArmyChanged method clears the command stack when the army is changed (e.g. a new army is created or an old one is loaded)
comment:8 Changed 10 years ago by
released: | 1 → yes |
---|
Mark released fixes as released using radio values
Can't recreate with opening an army and closing it, or with creating a new army and closing it without making changes. Needs a repeatable test case.