From a7ec10525e04c4623773951320fd228bbbabd6af Mon Sep 17 00:00:00 2001 From: blitzmann Date: Wed, 12 Apr 2017 00:34:50 -0400 Subject: [PATCH] Apparently this happens on command fits as well... temp fix until I can look into why this happens --- eos/saveddata/fit.py | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/eos/saveddata/fit.py b/eos/saveddata/fit.py index 014c69fa6..2449e7e9a 100644 --- a/eos/saveddata/fit.py +++ b/eos/saveddata/fit.py @@ -689,7 +689,10 @@ class Fit(object): # For fits that are under local's Command, we do the same thing for value in self.boostedOnto.values(): - value.boosted_fit.__resetDependantCalcs() + # apparently this is a thing that happens when removing a command fit from a fit and then switching to + # that command fit. Same as projected clears, figure out why. + if value.boosted_fit: + value.boosted_fit.__resetDependantCalcs() # it should be noted that command bursts don't affect other command bursts