You are here: MyURC.org > V2SimEnv > Trace URC Simulation Environment - Release Notes

Trace URC Simulation Environment - Release Notes

Release 3.2 - October 2006

Note: Since this version is based on URC SDK 3.2, its number is 3.2 too.

Changes to Version 3.1

• New Target:
  • Elevator simulation, written in C (available only as application)
• URC implementations:
  • Swing Client:
    • DateTime, Date, Month, YearMonth, Day, MonthDay Interactors implemented
    • Duration Interactor implemented
    • incremental attribute implemented in SwingRange
  • Text Client (very simple UI, only as application)
    • DateTime, Date, Month, YearMonth, Day, MonthDay Interactors implemented
    • operationRef parsing implemented for the range interactor.

Known Limitations

• Text Client
  • Does not support mulitiple languages
  • Not all interactors implemented
  • Use of locators not implemented
  • Does not support stacked modal dialogs
  • Does not support Duration Interactor.
• Swing Client
  • Does not display help resources
  • Locators not completely functional
  • Not all all interactors implemented
• TV
  • The controls for "Contrast" and "Brightness" have no effect
• Elevator
  • The elevator only runs from the batch file, and not from Eclipse
  • The "Open Door", "Close Door", "Emergency Signal" and "Firefighter Controls" commands have no effect
  • The elevator does not take commands through the command prompt, and there is no way the stop it through the prompt. Because of this, the elevator does not unbind from the TUN when it is closed. Also, temporary files for TUN communication purposes are not deleted after closing.
  • Multiple sessions have not been tested

Note: The client reads the target's documents from the local filesystem. Therefore you can only run a client and target from different computers if both computers have the documents stored locally in the same file locations.

Known Bugs

• Swing Client
  • Language switching doesn't work correctly sometimes.
• Discovery between targets and clients does not always work. If discovery doesn't occur after about twenty seconds, close the applications/applets and try running the target and the client in different orders, with different amounts of time between starting each one.
• Running multiple TV applets at the same time causes unexpected behaviors with the playing of mpegs.
• Some of the elevator elements, including elevatorFloor and userFloor, do not display on the SwingClient.
• The elevator has not been rigorously tested, and some combinations of inputs seem to freeze or crash it.

---

Last update: Jamie Tabaka, 2006-10-18