[orca] Get rid of the forced-qui-prefs when there are no settings.



commit 807c963928a04038c430aeb6ba5cd9043e1394cc
Author: Joanmarie Diggs <jdiggs igalia com>
Date:   Sat May 12 00:09:33 2012 -0400

    Get rid of the forced-qui-prefs when there are no settings.
    
    This brings us into alignment with what we do in a terminal/
    console. Plus, everyone is surpressing this capability anyway.
    And today is housecleaning day. :)

 src/orca/orca.py |   12 +-----------
 1 files changed, 1 insertions(+), 11 deletions(-)
---
diff --git a/src/orca/orca.py b/src/orca/orca.py
index e7f2596..b1471e5 100644
--- a/src/orca/orca.py
+++ b/src/orca/orca.py
@@ -1452,19 +1452,9 @@ def main():
 
     # Check to see if the user wants the configuration GUI. It's
     # done here so that the user's existing preferences can be used
-    # to set the initial GUI state.  We'll also force the set to
-    # be run if the preferences file doesn't exist, unless the
-    # user has bypassed any setup via the --no-setup switch.
-    #
+    # to set the initial GUI state.
     if options.setupRequested and not options.bypassSetup and options.showGUI:
         showPreferencesGUI()
-    elif not options.bypassSetup \
-         and (not _userSettings or _settingsManager.isFirstStart()):
-        if options.desktopRunning:
-            showPreferencesGUI()
-        else:
-            _showPreferencesConsole()
-        _settingsManager.setFirstStart()
     elif options.bypassSetup:
         loadUserSettings(skipReloadMessage=True)
         _settingsManager.setFirstStart()



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]