i think by the latter option you mean standardising the datatypes of entry and output - that wasn't so much what i was getting at i think though others may find that useful
its more to repeat code chunks which of course implies that the inputs and outputs remain the same On Oct 16, 11:10 pm, taz <[EMAIL PROTECTED]> wrote: > That's an interesting idea... something similar to Maya where scripts > can be docked on a "custom" tab? > > Is it more important to have vb/c code handy or is it more the desire > to preserve established vb/c input and output parameters so they don't > need to be set up each time? > > Or is it best to keep everything together? > > Just expanding on the wish... > > taz > > On Oct 16, 4:06 am, David Rutten <[EMAIL PROTECTED]> wrote: > > > > > UrbSur, > > > Good idea, I'll look into this after I'm out of data-structure-h*ll > > > -- > > David Rutten > > Robert McNeel & Associates > > > On Oct 15, 7:16 pm, urbansurgery <[EMAIL PROTECTED]> > > wrote: > > > > An additional category panel of preused vb/c objects would be dead > > > handy for reusing previously scripted objects across projects- Hide > > > quoted text - > > > - Show quoted text -- Hide quoted text - > > - Show quoted text -
