Version 1.1 Released

Version 1.1 has been released to address several bugs that have been discovered. This release corrects a number of stability issues and has efficiency improvements to multiple pieces of existing functionality.

Change Log:

- RevComEngine_Core: When any function is called while RPG Maker is initially loading classes, an system failure error occurred. This was caused by trying to get the default dialog window color from the RPG Maker before they were loaded. The correction was to use hard-coded values until they become available after loading.
- RevComEngine_Core: When creating multiple windows, a system error would occur. This was caused by updating hash values while they were being accessed by other processes. This was corrected by implementing the existing safe hash updating process as part of window management.
- RevComEngine_Core: Ticket "Timer Calling Function That Creates Timer Fails" fixed where using timer within function called by a timer failed.
- RevComEngine_Core: Corrected where input box cursor was initially hidden from view.
- RevComEngine_Core: Corrected where, after changing the button's fonts, the change would not occur until a mouse event occurred to the button.
- RevComEngine_Core: Fixed issue where interactive element lists did not align properly.
- RevComEngine_Core: When setting input boxes' setting for returning entered text, a system occurred. This was fixed by correcting a syntax error.
- RevCommProcessor: Data processes can be run in async and sync modes. The async mode for speed with the possibility of the results coming back out of order, and sync mode is slower to keep results in order. The sync mode was initially built to operate as a sequential version of the async process which caused it not to operate as desired. This was fixed to make it a completely full and separate process. 
- RevCommServer: It was not allowing multiple instances of a data process transaction to be ran as it supposed to allow with transactions of any type. This was corrected.
- RevCommServer: It only allowed data events to return values back to the client side. This restriction was removed, so any form of database process can be made to return data to the client. Furthermore, the setting indicator that was required in the server configuration, "receive_msg", to allow processes to return data has been removed, and is not longer a requirement, allowing any database process to return data by default.
- RevCommServer: There was a failure of returning results of when multiple instances of a data process transaction due to the response ID for the instances being unavailable by the time it returns. The fix was to only pull the sets of results by transaction ID. There is a possibility that data sets being returned out of order, but efforts were made to sent them back in the order they were received.

Note: There are a number of new features that were part of 2.0 in the release. These are possibility partially implemented or developed. There will not covered in this documentation.