From 7df505834a27b9c6d1d525c871d12fb71a01bbbb Mon Sep 17 00:00:00 2001 From: Corollax Date: Fri, 29 Oct 2010 11:55:23 -0500 Subject: [PATCH] Restructured to make falloff calc act like optimal Should function identically, just looks cleaner. --- gui/builtinViewColumns/maxRange.py | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/gui/builtinViewColumns/maxRange.py b/gui/builtinViewColumns/maxRange.py index 6fc02fc3a..f5d25da04 100644 --- a/gui/builtinViewColumns/maxRange.py +++ b/gui/builtinViewColumns/maxRange.py @@ -52,10 +52,10 @@ class MaxRange(ViewColumn): def getText(self, stuff): maxRange = stuff.maxRange if hasattr(stuff, "maxRange") else stuff.getModifiedItemAttr("maxRange") falloff = stuff.getModifiedItemAttr("falloff") - if not falloff: - falloff = "" - else: + if falloff: falloff = "+%sm" % formatAmount(falloff, 3, 0, 3) + else: + falloff = "" if maxRange: return "%sm%s" % (formatAmount(maxRange, 3, 0, 3), falloff)