Thanks David.  Is there an ETA for the next release of GH?  What about
Rhino 5?

On Mar 10, 8:36 am, David Rutten <[email protected]> wrote:
> Just save them as gh or ghx files using your current version.
> Grasshopper 0.5 and earlier will load wrm and save as ghx. We'll keep
> an old version of Grasshopper around in case you run into more wrm
> files that need converting, but this will become a time and effort
> intensive process once 0.6 hits the shelves.
>
> My previous comment about the file not working wasn't an IO problem.
> Old gh and ghx files should read fine (if they don't, I'll fix it).
> The comment was about them working differently. The data matching
> logic has changed so you may have to tweak old files before they
> behave as before.
>
> --
> David Rutten
> [email protected]
> Robert McNeel & Associates
>
> On Mar 10, 3:30 pm, baldino <[email protected]> wrote:
>
> > uh, good to know
>
> > you said in a previous post that our actual ghx definitions might not
> > work correctly in the next GH version...
> > will you implement a "compatibility mode" or something...
> > or will it be possible to install the new gh along with the older
> > version ?
>
> > On Mar 10, 2:56 pm, opposablethumbs <[email protected]> wrote:
>
> > > Is there an easy way to convert a bunch of files?
> > > If not no big deal.
>
> > > thanks.
>
> > > David Rutten wrote:
> > > > The next version of Grasshopper will no longer support the *.wrm file
> > > > format. If you still have wrm files you should convert them now into
> > > > either *.gh or *.ghx.
>
> > > > Support for this file format was intrinsic to many different
> > > > interfaces and classes and in the interest of simplicity I decided to
> > > > remove legacy IO code from the core plugin.
>
> > > > --
> > > > David Rutten
> > > > [email protected]
> > > > Robert McNeel & Associates

Reply via email to