- Deleted platform specific folders from xpcPlugin folder.
- Added new XPlaneConnect folder under xpcPlugin folder.
- Moved and renamed windows binaries into architecture specific folders
- Moved and renamed mac binary to XPlaneConnect root (single mac binary supports 32 & 64 bit)
- Updated installation instructions in Readme
- Cleaned up plugin Visual Studio project architecture
- The MSVC runtime is now statically linked for the 32bit and 64bit Windows plugins. This is done to avoid potentially requiring users to install an additional package from Microsoft to use the plugin.
- The "Release" build configuration has also been removed, since it was not configured correctly. It will be re-added at a later date.
- Temporarily disabled the sending of a CONF message from the plugin in response to setCONN. The CONF message causes crashes on Windows 8 when setCONN is called multiple times.
- Removed code that attempted to free result slots in parseRequest before overwritting them with new allocations. The CTests suite currently calls parseRequest with a multidimensional array allocated on the stack, resulting in an attempt to free stack memory. A better solution may be to simply check whether the existing result slots are long enough.
- As of this commit, all tests in the CTests suite are passing on Windows 8 for X-Plane 9, X-Plane 10 23bit and X-Plane 10 64bit.
- Fixed incorrect message buffer size in sendCTRL function.
- Fixed a bug in sendCTRLTest where not all DREF sizes were being set.
- Increased message buffer size in sendReadTest to account for assumptions made by sendUDP.
- Fixed a bug in updateLog where the log message would sometimes start with several null characters, causing the log message to be effectively ignored by fprintf.
- The xpcPlugin Visual Studio solution now supports 32 bit and 64 bit builds.
- Logging performed by the plugin now works correctly on Windows.
- Long log messages are now truncated to 500 characters. Previously, messages over 500 characters would be omitted, and an error message logged in their place.
- Several files which were incorrectly added to source control have been deleted.
- Include paths were specified with absolute paths, which break as soon as the project is moved to a different location. (e.g., when cloning to a new computer from GitHub).
- Include paths are now specified relative to the project file, so everything should work as long as the entire XPC directory is present.
