Petr, Yes, totally! I had plenty of confused times with VID. But I don't think a "brute force" copy/deep function helps at all. The problem is one of understanding. We need nice tools for seeing the situation, not just blindly copying everything. You see what I mean? When we want to copy things, we want to be selective, otherwise we become very inefficient.
I think a deep/copy would be useful for VID only if it has really good options for selective copying. It must be able to ignore certain objects like system/view/vid etc. Such a useful function is very hard to write and would require lots of tweaking and maintenance as View and VID evolve. (I think so anyway, maybe not). Anton. > Anton wrote: > > >You are talking about deep copy, no? > >What if the object contains a reference to the > >system object, for example? Or, as is common, > >'parent-face ? > >What are you going to do, copy the system object into > >your new object? > > > Surely not, that's what copy/deep would be good for - to have an > option ... > > >Anyway, if you need that kind of functionality, (and I don't > >think you really do), then I think Ladislav's evaluation.r > >does it. I haven't tried it out though. > > > >I am curious, Boleslav, if you are still confused about anything. > > > I can't agree here. Now tell me Anton, if you had never any kind of > problem playing with VID, while ending up with confused UI, shared > edges, feels, or other sub-objects? Just curious ... as if not, we are > probably all dumb here in CZ then ;-) > > -pekr- -- To unsubscribe from this list, please send an email to [EMAIL PROTECTED] with "unsubscribe" in the subject, without the quotes.
