lesbentley opened this issue on Aug 17, 2002 ยท 7 posts
VK posted Sun, 18 August 2002 at 7:14 AM
Well, I don't know if 'forceLimits' 1 or 'forceLimits' 4 makes any difference. I think 'forceLimits' is a flag, which can be 0 (off) or any other value (on). If you choose for example a 'forceLimits' 1, 4, 32, or -100 in the library code, Poser sets the flag always to 4. That's why I'm using 4, because this is the 'correct' value. But you can choose 1, -100, 666, or something else, if you like. All values force the channel to the 'min' and 'max' limits. BTW, if you activate the 'Use Limits' menu command, the 'useLimits' flag in the 'doc' clause is set to 1, which forces all channels to the 'min' and 'max' limits (including the channels of cameras, lights, etc.). The 'useLimits' flag doesn't lock the dial itself (the slider in the dial palette), whereas the 'forceLimits' flag forces the channel values and the dial to the 'min' and 'max' limits. I guess the 'forceLimits' flag is stored in the third bit of a binary value, which is the integer value 4. The 'customMaterial' flag is stored as 0 (off) or 32 (on), for example. This could be the sixth bit of a binary value.