|
Notes |
|
|
(0006042)
|
|
Clinton Stimpson
|
|
2006-12-21 18:27
|
|
How about the server manager updating the domains ranges for us with these tied properties?
If there are two properties, lower and upper threshold, and it ranges between 0 and 1.
If the value of the lower threshold is 0.5, the domain for the upper threshold could be 0.5 to 1.
The sliders and combo boxes already listen for domain change events from the server manager and would automatically update.
This will work better for the auto panels. Or the GUI would have to find query to see if any properties are tied to each other, is it possible to query that? Or, we'd just have to do it in custom panels.
Utkarsh, any thoughts?
|
|
|
|
(0006043)
|
|
Utkarsh Ayachit
|
|
2006-12-22 09:45
|
|
That sounds like a good idea.
Things to note here:
* The two values (lets call them min/max) may be two components of the same property (such as ThresholdBetween property of the Threshold filter) or two different properties (such as StartTheta and EndTheta of SphereSource). The domain should be able to handle both cases.
* This functionality will be added to a couple of new IntRangeDomain and DoubleRangeDomain subclasses, say SomeNewRangeDomain. In that case, a property with such dynamic ranges, consider "ThresholdBetween", may have more than 1 domain (in our case "ArrayRangeDomain" and "SomeNewRangeDomain"). The GUI must be able to take intersection of the ranges specified by the two (or more) domains as the actual range for the property.
* Since now a Domain may have a required property as the property to which the Domain belongs, we will run into reference loops. It shouldn't be a big deal to fix this, but noted here to make sure we don't miss this. |
|
|
|
(0006044)
|
|
Clinton Stimpson
|
|
2006-12-22 11:46
|
|
I was thinking...
If we have min/max for a threshold, and the min is at 0.5 and the max is at 0.5, if the domains are 0,0.5 and 0.5,1 then the GUI will have no idea that the min can go higher or that the max can go lower. So I'm not sure I'd change the domains like that.
So the GUI doing intersections sounds good, and having those domain subclasses means the GUI would know how to do that.
|
|
|
|
(0006072)
|
|
Ken Moreland
|
|
2007-01-03 16:58
|
|
|
Before implementing this, I recommend looking at the QRangeSlider widget in vtkSNL. This widget is designed to provide the user with a min/max range and is much more usable than a pair of sliders. |
|
|
|
(0008416)
|
|
Clinton Stimpson
|
|
2007-08-13 10:55
|
|
|
If we had the QRangeSlider from vtkSNL, the GUI would still need help deciding when to use it when automatically creating panels. That's what the new IntRangeDomain and DoubleRangeDomain subclasses would do. So the server manager side of it needs to be done before we can use QRangeSlider. |
|
|
|
(0023874)
|
|
Dave DeMarle
|
|
2010-12-10 13:40
|
|
|
This has been resolved with the creation of range domains. |
|
|
|
(0023943)
|
|
Alan Scott
|
|
2010-12-13 17:15
|
|
|
Trusting Dave's opinion on Range Domains. |
|