6.5 was a developer preview of some very big changes. I would not have recommended running it on a stack that was not backed up in another location.
In fact, Mr. Beaumont actually had this at the very beginning of that email: We are pleased to announce the release of LiveCode 6.5.0 DP1. > *WARNING*: This is a DEVELOPMENT release (alpha). It's purpose is to put > new features into the hands of the LiveCode community for testing and > feedback. Please backup your stacks before opening them. On Thu, Sep 12, 2013 at 6:39 PM, Vaughn Clement <vclem...@gmail.com> wrote: > Hi Everyone > > I just updated to the newest update for LiveCode 6.5 > > I then had a surprise when I opened the last stack project I was working on > and it's now corrupted and won't open. I have a backup from this morning, > but I lost all the scripting I did during the day. Is anyone else getting > this kind of issue? > > > Thank you > > Vaughn Clement > > Apps by Vaughn Clement (Support) > *http://www.appsbyvaughnclement.com/tools/home-page/* > Skype: vaughn.clement > https://secure.join.me/appsbyvclement > FaceTime: vclem...@gmail.com > LogMeIn also avaialble > Call on "ooVoo" at address: vaughnclement or 9282549062 > Ph. 928-254-9062 > Cloud Hosting Registration Web Site: > https://my.oditech.com/cart.php?a=add&pid=41 > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > -- Regards, Andrew Kluthe and...@ctech.me _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
