[tor-commits] [arm/release] fix: Config value changes weren't being reflected

atagar at torproject.org atagar at torproject.org
Sun Jul 17 06:08:19 UTC 2011


commit 8e90af9c9eb4af4f3fa12d7f12c19279314d8b64
Author: Damian Johnson <atagar at torproject.org>
Date:   Mon May 9 22:04:21 2011 -0700

    fix: Config value changes weren't being reflected
    
    When a value was edited in the configuration panel the listed value didn't
    change (though it did in other places like the detail panel). This was due to a
    cached copy of the display element. Flushing this cache when editing values.
---
 src/cli/configPanel.py |    3 +++
 1 files changed, 3 insertions(+), 0 deletions(-)

diff --git a/src/cli/configPanel.py b/src/cli/configPanel.py
index 37b7ddb..b6fba8b 100644
--- a/src/cli/configPanel.py
+++ b/src/cli/configPanel.py
@@ -293,6 +293,9 @@ class ConfigPanel(panel.Panel):
             
             torTools.getConn().setOption(configOption, newValue)
             
+            # forces the label to be remade with the new value
+            selection.labelCache = None
+            
             # resets the isDefault flag
             customOptions = torConfig.getCustomOptions()
             selection.fields[Field.IS_DEFAULT] = not configOption in customOptions





More information about the tor-commits mailing list