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.

Sign up for GitHub

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

Jump to bottom

Clear Result Info and Result Plot when closing a case #225

Closed
hhgs opened this issue Aug 22, 2014 · 3 comments
Closed

Clear Result Info and Result Plot when closing a case #225

hhgs opened this issue Aug 22, 2014 · 3 comments
Labels
BugInRelease Bug in an official release
Milestone
Maintenance Nov 2016

Comments

@hhgs
Copy link
Member

hhgs commented Aug 22, 2014

No description provided.

@hhgs hhgs added the bug label Aug 22, 2014
@JacobStoren JacobStoren added BugInRelease Bug in an official release and removed Bug Bug not yet in an official release labels Nov 11, 2015
@hhgs hhgs modified the milestones: GeoMech Sprint 4 Suggested Additions, Maintenance I May 25, 2016
@JacobStoren
Copy link
Member

Is it ok to do that Independently of which case produced the Result Info ?
If not, the task is larger.

@hhgs
Copy link
Member Author

hhgs commented May 30, 2016

For the users it only makes sense to clear Result Info, if the case shown in Result Info is closed.

@magnesj
Copy link
Member

magnesj commented Jul 18, 2016

Implemented clear of Result Info and Result Plot when closing a case. It will be a larger task to clear only information coming from the case being closed.

@magnesj magnesj changed the title Clear Result Info when closing a case Clear Result Info and Result Plot when closing a case Jul 18, 2016
magnesj added a commit that referenced this issue Jul 18, 2016
@magnesj
#225 Clear Result Info and Result Plot when closing a case
fa19a74
@magnesj magnesj closed this as completed Jul 18, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
BugInRelease Bug in an official release
Projects
None yet
Milestone
Maintenance Nov 2016
Development

No branches or pull requests
3 participants
@hhgs @magnesj @JacobStoren