|
rilos
rilos
|
1. When adding a slider to one component-input the slider should per default take the actual value the input field has in the component. Otherwise you have normally to reset the slider, to the value the field had before (this is just time consuming).
2. When you want to have control over some component setting in the final filter, you alwas have to drop one kind of slider to the input-field. Wouldnt it be easer to provide a flag with each relevant input field to say I would like this setting in the final filter control ?
Would be much easier and time-saving (also saving editor workspace). regards, rilos |
| Posted: June 9, 2006 7:46 am |
Details
E-Mail
|
|
Lucato
FF addicted
|
| Quote |
|---|
| 1. When adding a slider to one component-input the slider should per default take the actual value the input field has in the component. Otherwise you have normally to reset the slider, to the value the field had before (this is just time consuming). |
- Good request Rilos, I vote for that too. This bothers a little now a days. Several times I have to disconnect to see how was the value in the component.
| Quote |
|---|
| 2. When you want to... |
- Hmmm...I didn't get to understand this one. Maybe my English isn't so good today. I need to practice a little more. Could you say in another words? Well, let me wait some feedback from somebody that got It.
|
| Posted: June 9, 2006 8:02 am |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
| Quote |
|---|
rilos wrote:
Wouldnt it be easer to provide a flag with each relevant input field to say I would like this setting in the final filter control ? |
Dedicated control components have three important advantages over this:
1. You can use Remappers to specify how exactly the conrol component affects the input it is connected to.
2. You can control multiple inputs with a single Control component, and each of these multiple inputs can be Remapped.
3. You can give the control a custom name (localizable in future versions).
|
| Posted: June 9, 2006 8:42 am |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
| Quote |
|---|
rilos wrote:
When adding a slider to one component-input the slider should per default take the actual value the input field has in the component. |
Technically, this means Backward Remapping. The programmers will kill me if I add this to the short-term list 
|
| Posted: June 9, 2006 8:43 am |
Details
E-Mail
|
|
Lucato
FF addicted
|
| Quote |
|---|
| Technically, this means Backward Remapping. The programmers will kill me if I add this to the short-term list |
Backward Remapping??? More or less, it is just make the slide/Controls read the values input when connected the first time instead of using their default values. 
|
| Posted: June 9, 2006 12:07 pm |
Details
E-Mail
|
|
byRo
an Englishman in Brazil
|
| Quote |
|---|
Vladimir Golovin wrote:
Technically, this means Backward Remapping. The programmers will kill me if I add this to the short-term list |
I can sympathize that this could quickly escalate into something complex - going backwards through the remappers, controls already connected to other inputs
However, I must also side with rilos and Lucato. When you connect a new Control to an input and the control doesn't adopt the input's value, it just seems...well, wrong  .
Rô
_________________________________
My favourite question is "Why?".
My second favourite is "Why not?"
|
| Posted: June 9, 2006 12:22 pm |
Details
E-Mail
|
|
byRo
an Englishman in Brazil
|
I got it!!!
When you add a new Control, it assumes the name of the input to which it was connected.
That's why it seems so strange that it doesn't also assume the value  .
So it's going to be real easy to implement, isn't it? 
Rô _________________________________
My favourite question is "Why?".
My second favourite is "Why not?" |
| Posted: June 9, 2006 2:27 pm |
Details
E-Mail
|
|
rilos
rilos
|
@Vlad: I agree with your 3 points to the second idea (altough it would be nice in some cases where you dont need to remap and reuse).
I dont understand the problem in the first idea (default value of new sliders set to the actual component value). With my "historical" programming knowledge this one should be quite easy to solve  - and it would help much. regards, rilos |
| Posted: June 12, 2006 3:30 am |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
| Quote |
|---|
byRo wrote:
So it's going to be real easy to implement, isn't it? |
If it was, it would be already implemented -- it is an obvious enhancement and it was on my list.
| Quote |
|---|
byRo wrote:
That's why it seems so strange that it doesn't also assume the value |
In Filter Forge you can connect anything to anything -- not only sliders to sliders. What value should a Slider Control assume when it is connected not to a slider but to a color input, a checkbox, or a list?
|
| Posted: June 12, 2006 1:13 pm |
Details
E-Mail
|
Vladimir Golovin
Administrator
|
| Quote |
|---|
byRo wrote:
it assumes the name of the input to which it was connected. |
The name is just a string, and to "assume" it we don't have to do any conversions (or remappings, to be precise).
|
| Posted: June 12, 2006 1:16 pm |
Details
E-Mail
|
