Hi David, Yes that is what I expect to get.
So what does "making a local copy first" look like? Should I have a different setup to do this now? Why does the XY plane and XYplane+ Plane work but not the surface? Is that what you meant by missed a few cases? Do I have the latest version? Thanks, Chris K. Palmer On Nov 3, 2:27 am, David Rutten <[EMAIL PROTECTED]> wrote: > Hi Chris, > > is > this:http://grasshopper3d.googlegroups.com/web/BugDemoFixedQuestionMark.jp... > > what you expect to get? If it is, it seems I've already fixed the > issue. A while back I stopped making copies of all data at every > junction in order to improve performance and reduce memory overhead, > however it means that if a component now changes data, it is > responsible for making a local copy first, otherwise it will mess up > data which is shared among multiple components. > I missed a few cases the first time around. > > -- > David Rutten > Robert McNeel & Associates > > On Nov 1, 5:11 am, ckpalmer <[EMAIL PROTECTED]> wrote: > > > Hello David, > > > First I would like to thank you for the wonderful Grasshopper plugin > > that I have been enjoying for some time now. I use it extensively in > > my teaching at Colorado University in the Architecture Department. > > I'll have lots to share after this semester ends when I will hopefully > > have time to polish up tools developed with your amazing software for > > public consumption. > > > I have posted a rhino and grasshopper file (bugDemo.zip) that shows a > > problem I noticed with referenced geometry in the newest Grasshopper > > that used to work the way I illustrated but now does not. > > > Thanks in advance for your attention to this, > > > Chris K. Palmer
