Originally submitted to Google Code by c.martin.taylor on 14 Apr 2010
The easiest way to reproduce and see this bug is to unzip the attached file and try to open RIDE 0.22.1 in the RIDE_RemoteLibraryBug folder (you can use the RobotIDE.bat in Windows). It is my belief that the fix for Issue 393 may have caused this new issue.
We do this kind of Remote library reference A LOT at TI, so this bug is forcing our test developers to keep back at version 0.19 of RIDE (where this bug does not exist), rather than upgrading to 0.21 or 0.22.1 (where this bug does exist).