Cage opened this issue on Dec 20, 2006 · 1232 posts
Spanki posted Fri, 18 April 2008 at 3:02 PM
I'm still busy with other things, so I can't comment on all of the above yet, but...
**re: delete vs re-assignment...
**
Whether you just re-assign some variable or specifically delete it first should result in exactly the same thing...
- When you re-assign it, it essentially "falls out of scope" (as far as the interpreter is concerned), so before assigning the new value to it, the interpreter (should) decrement it's reference count on that variable (potentially freeing the memory it uses if the reference count hits zero), then it assigns it to the new value.
...again, I haven't had the time to look at the links you posted earlier, so if there's some bug in the interpreter that I'm not aware of, that might change things.
**re: hit distance -> .vwt file
**
I'm not opposed to this in general, except for the fact that... that distance is dependant on the conditions at the time that the correlation was done (morphs in play, world-space positions, etc) which is lost / not tracked in the .vwt file (and I'm not suggesting it should be :) ).
On the other hand, so is the rest of the data in the .vwt file, so it's probably no big deal.
re: actors, comments, etc.
I hate to comment on this without taking the time to re-aquaint myself with the entire .vwt file format and all related issues... .I know I've had multiple suggestions early on that were related to this particular subject, that may or may not have ever been implemented.
But in general, I'm not opposed to putting whatever you want in a comment record, until/unless it starts getting parsed by the script, in which case it should no longer really be a 'comment', but some (new) record type, instead.
Cinema4D Plugins (Home of Riptide, Riptide Pro, Undertow, Morph Mill, KyamaSlide and I/Ogre plugins) Poser products Freelance Modelling, Poser Rigging, UV-mapping work for hire.