system/src/sc/lang/AbstractInterpreter.java
public boolean pushCurrentScopeContext() {
      if (currentScopeCtx != null)
         System.err.println("*** Nested pushCurrentScopeContext calls in interpreter!");
      CurrentScopeContext ctx = CurrentScopeContext.get(scopeContextName);
      if (ctx != null && ctx != CurrentScopeContext.getThreadScopeContext()) {
         CurrentScopeContext.pushCurrentScopeContext(ctx, true);
         currentScopeCtx = ctx;
         return true;
      }
      return false;
   }
/**
    * Before we run any object resolveName methods or expressions from the command, we may need to select a CurrentScopeContext that's
    * been registered by the framework, to select the specific context these commands operate in.  For example, when the command
    * line is enabled, each time we render a window, we switch to the current scopeContextName's context so we can control a specific
    * collection of state with the right locks to operate in that context.  The defaultCmdContext can be updated to point to the most
    * logical state based on the developer's current context (e.g. the last web-page loaded).
    */
Before we run any object resolveName methods or expressions from the command, we may need to select a CurrentScopeContext that's
been registered by the framework, to select the specific context these commands operate in.  For example, when the command
line is enabled, each time we render a window, we switch to the current scopeContextName's context so we can control a specific
collection of state with the right locks to operate in that context.  The defaultCmdContext can be updated to point to the most
logical state based on the developer's current context .
Before we run any object resolveName methods or expressions from the command we may need to select a CurrentScopeContext that ' s been registered by the framework to select the specific context these commands operate in . For example when the command line is enabled each time we render a window we switch to the current scopeContextName ' s context so we can control a specific collection of state with the right locks to operate in that context . The defaultCmdContext can be updated to point to the most logical state based on the developer ' s current context .
public boolean pushCurrentScopeContext() {
      if (currentScopeCtx != null)
         System.err.println("*** Nested pushCurrentScopeContext calls in interpreter!");
      CurrentScopeContext ctx = CurrentScopeContext.get(scopeContextName);
      if (ctx != null && ctx != CurrentScopeContext.getThreadScopeContext()) {
         CurrentScopeContext.pushCurrentScopeContext(ctx, true);
         currentScopeCtx = ctx;
         return true;
      }
      return false;
   }
public boolean pushCurrentScopeContext ( ) { if ( currentScopeCtx != null ) System . err . println ( "*** Nested pushCurrentScopeContext calls in interpreter!" ) ; CurrentScopeContext ctx = CurrentScopeContext . get ( scopeContextName ) ; if ( ctx != null && ctx != CurrentScopeContext . getThreadScopeContext ( ) ) { CurrentScopeContext . pushCurrentScopeContext ( ctx , true ) ; currentScopeCtx = ctx ; return true ; } return false ; }
Before we run any object resolveName methods or expressions from the command, we may need to select a CurrentScopeContext that's
 been registered by the framework, to select the specific context these commands operate in.
Before we run any object resolveName methods or expressions from the command we may need to select a CurrentScopeContext that ' s been registered by the framework to select the specific context these commands operate in .