Eyeon Talk:Script/Reference/Applications/Fuse/Classes/Input/RangeControl

From VFXPedia

I've noticed that the standard tools in Fusion typically are set up so that if you type in a value for the low range that is higher than the high range, the high range gets modified so it is the same as the low range. By default, a fuse using a range control will not allow you to type in a low range that is higher than the high range. Is there a special attribute for this behaviour, or is it supposed to be done through NotifyChanged? --Chad 14:51, 16 April 2010 (EDT)

There's nothing special a tool (or fuse) has to do, as that behaviour is automatically provided by the range control. --Stuart 16:28, 16 April 2010 (EDT)

I'll go back through our code, but so far, none of our fuses or plugins with range controls does this. --Chad

Fog3D doesn't do the automatic offset, but SoftClip3D does. Unfortunately, only Fog3D is in the SDK, not SoftClip3D. --Chad

Fog3D does do the 'automatic offset' AFAICT. Set its far distance to something like 50, then set the near distance to 75, and the far distance will be moved to 75. --Stuart

Not here, at least. The default is 0/100. Typing 200 into the Near results in 100/100. Then typing 30 into Far results in 100/100. Typing 0 into Near and 75 into Far gives 0/75, and THEN typing 80 into Near results in 80/80. So something is weird, at least on my end, with x64 build 511 and Windows 7. --Chad

Yes, the default is 0/100, which is why I said to change that to 0/50 before then entering 75/50, which becomes 75/75. If the upper visible limit is 100, then attemping 200/100 will not push it to 200/200 - it'll keep it at 100/100 - the upper visible limit. --Stuart 17:42, 21 April 2010 (EDT)

But other tools, like say, SoftClip, work just fine from the default values. --Chad

SoftClip's default upper value isn't already the upper visible limit, with Fog it is. --Stuart 14:03, 23 April 2010 (EDT)

Ah, OK. Now I see the difference... Thanks. --Chad

The text says "Set the input which will represent the Low value to have a IC_ControlID of 1, and the input which represents the High value to IC_ControlID of 2. See the example below." But the example shows 0 & 1. --Chad 15:11, 13 October 2010 (EDT)

It should be 0 and 1 (ie. the same as RANGECONTROL_LOW and RANGECONTROL_HIGH in the C++ SDK). --Stuart 15:52, 14 October 2010 (EDT)