The risk is much the same as using actual values in code instead of
pre-defined constants. They may well not change but there's still a
possibility that they might. When I think about doing something like this I
run through in my mind what may happen if a bunch of ClassIDs change at any
time in the future. Then I think about what might happen if I find out about
it against a deadline. Then I look for another way of doing it.
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
> Behalf Of Julian Johnson
> Sent: 29 January 2008 12:59
> To: XSI(at)Softimage.COM
> Subject: Re: [Scripting] Using FindChildren to find Hair/HairSimOps
> etc...
>
> Dan Yargici wrote:
> > Thanks! Are there any potential drawbacks with using this method?
> > Will these be different in, say, XSI v11?
> Unless Soft change the ClassIDs of some of these objects I think it's
> pretty robust..it's definitely one of the recommended techniques in the
> scripting section of the XSI Wiki so I guess it's safe for a while yet!
>
---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi
