Version 2.0 - Final Release

This is the final release for RevComEngine with version 2.0. Usage examples are available on the Wiki. It includes the following new features and fixes:

• User Sessions: A login process that allows users to be connected clients in RevCommServer for operations in database tracking.
• Timers: The functionality has been overhauled to remove types and all timers can be set to run continuously or for a number of intervals, and pass parameters to called functions.
• Bars: Updated functionality to automatically update the bar's visible state when its values change.
• Downloads: Fixed issue where multiple downloads running at the same time have a high change of failure. This issue has been corrected by queuing download files individually.
• Bars: Fixed issue were setting bars through interface caused an error, This has been corrected.
• Server Connection: Changed default RevCommServer connection port from 40000 to 59234
• Downloader Install: The install scripts for the Downloader functionality has been included with the install script for Release 2.0.
• Map Events: There was an issue where the event would not fire on the last map with the highest number ID. This was corrected.
• Image Load: An error would occur if an image resource had been released when it was attempted to be retrieved.
• Memory Resource Release: Improvements were made to release resources. This includes options for releasing image and interface resources.
• Interface Text: There was an issues where text was not space appropriately within the area of the interface. This has be corrected.
• Interface Component Movement: There was an issue where components within an interface would not reposition appropriately with the interface's movement. This has been corrected.
• Interface Blinking: When the interface was in blink mode, there was an issue where the blinking was inconsistent. This has been corrected.
• Scene Events: The ability to setup events on scene change removed. This functionality had multiple issues that can not be resolved, so it was removed.