There's also the question of ease, consistency and reliablity. The
collection method always works, always the same way and it's quick and easy
to use taking whatever's been slung up in the history pane during
interaction. Digging around for the OM method can be time-consuming. It also
handles wild cards easily and if it returns nothing you can be absolutely
certain the object doesn't exist, rather than that you may or may not have
used the correct method.
Wrap it in a function.
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM
> [mailto:owner-xsi(at)Softimage.COM] On Behalf Of brad
> Sent: 25 July 2005 03:29
> To: XSI(at)Softimage.COM
> Subject: Re: [script] finding Custom Pset
>
> Point taken. But then, fewer lines doesn't necessarily mean
> faster performance. In fact, that collection technique I
> originally posted is often faster (surprisingly) than many of
> the examples found in the XSI docs for accessing objects.
>
> One of these days, I'll post a function I've used for sorting
> out which Models are currently selected in a scene. The
> fewest number of lines to do it is 4, but the performance is
> slow for large scenes. I found a technique that's 10 times
> faster but requires more than 12 lines of code... strange but
> true. :-)
>
> -Brad
>
> -------Original Message-------
> > kim aldis wrote:
> >
> > >Just out of curiosity, why would it matter to you what method you
> > use as >long as it works?
>
> > Hi Kim:
> >
> > Trying to reduce the number of lines in my code, also if I can get
> > the same result with lesser lines why not use it :-)
> >
> > Biju
> > ---
> > Unsubscribe? Mail Majordomo(at)Softimage.COM with the
> following text in body:
> > unsubscribe xsi
> >
> -------Original Message-------
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following
> text in body:
> unsubscribe xsi
>
>
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
