Toolbar

• Run
  Hitting the run button starts the application. If the run button becomes greyed out, that means that multiple instances of the application may not be started; it will become reactivated when the application completes.
• Log
  All the output (stdout/stderr) from the fiswidget application that is sent to the output window can be captured and written to an ascii logfile as well. The log button invokes the logfile information box, which has the following fields:
  • logfile
    Enter the name of the logfile.
  • Logging is:
    Use the checkbox to turn logging on/off.
  • OK
    Accept these logfile settings.
  • Cancel
    Ignore these logfile settings, revert to previous settings.
• Server
  If this button is enabled, then the backend program can be run on another machine across a network. To get an overview about running in client / server mode, click here. The server button invokes the server information box, which has the following fields:
  • Use remote server
    Check the check box and enter the name of the machine to connect to.
  • Username
    Type in the username that the FisServers are running under.
  • Password
    Type in the password to log into the FisServer.
  • Change WD in all GUI textfields
    Replace all occurances of the current working directory with new working directory in any text fields in the GUI.
  • Change current working directory
    Check this to change the current working directory of the FisServer.
  • Current WD
    This is the current working directory of the FisServer.
  • New WD
    This is the directory that the FisServer should use as its new working directory.
  • OK
    Accept these settings.
  • Cancel
    Ignore these settings, revert to previous settings.
• Save
  Save the current settings of all the GUI components to an XML file for later reloading. The old GUI settings file (binary java serialization format) is still supported.
• Load
  Load all GUI fields from a saved XML/GUI settings file.
• Close
  Hitting the close button quits the entire application and all its associated windows. If the application has spawned a system process, ie a process that is running independently of the Java Virtual Machine, that independent process will not be killed by the close button.