Lucato
![]() |
When using the 'Switch' component and the control 'Checkbox', the 'Checkbox' has its default values as unchecked=5 and checked=8. I know we can 'Use Remmaping', but...
Wouldn't it be possible to make it as default unchecked=1 and checked=2? |
|||
Posted: October 8, 2008 5:50 pm | ||||
KGtheway2B
![]() |
+1
|
|||
Posted: October 9, 2008 12:18 am | ||||
jffe |
Aha ! For once, I totally 100% agree, the defaults of 5 & 8 are rather arbitrary, random, and dumb for that matter ha-ha.
![]() jffe Filter Forger |
|||
Posted: October 9, 2008 12:43 am | ||||
Kraellin
![]() |
+1 also.
If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: October 9, 2008 9:13 am | ||||
Betis
![]() |
+3
![]() Roses are #FF0000
Violets are #0000FF All my base are belong to you. |
|||
Posted: October 10, 2008 7:44 pm | ||||
Redcap
![]() |
+1 and +2 Get it because we want to change it to presets 1, and 2.... ![]() ![]() ![]() |
|||
Posted: October 10, 2008 11:02 pm | ||||
Vladimir Golovin
Administrator |
Yes, I remember being annoyed by this 5/8 thing. Honestly, I can't remember the reason why this is so. Probably, the unchecked state corresponds to the first third of the slider range (33.33333% rounded to the nearest integer) and the checked state to the second third (66.66666%). Anyway, I added this to the to-do list for future updates.
|
|||
Posted: October 14, 2008 3:20 am | ||||
Lucato
![]() |
Hey Vlad, good to hear from you! I hope you are ok dissapeared boy. :0)
Thanks for adding it into your to-do list. Have a great week. |
|||
Posted: October 14, 2008 4:52 am | ||||
GMM
Moderator
Posts: 3491 |
Lucato, the developers aren't happy with your suggestion
![]() This will require more code overhaul than it may seem for the first glance, not saying that we'll have to re-render the library filters. Looking forward to version 2.0... |
|||
Posted: October 14, 2008 5:23 am | ||||
Vladimir Golovin
Administrator |
Hehe
![]() I wanted to fix it in the nearest update, and we discussed this thing with the programmers. In short, our discussion went through two phases, "let's do it", and, after a minute of thinking, "uh-oh, we have a problem". The problem is that remappers in FF do not have a versioning system like that of components. So if we change the default values of the CheckboxToIntSlider remapper to 1/2 instead of 33.3%/66.6%, this will immediately affect all existing filters that use checkboxes connected to integer inputs with 'Use Remappers' turned off. Even if we modify all filters in the library, namely to turn Use Remapping on and set appropriate values for affected remappers, this change will still break the filters outside the library (My Filters, not submitted to the library). I'll keep it on the list anyway. |
|||
Posted: October 14, 2008 5:30 am | ||||
Lucato
![]() |
Come on guys, don't be lazy, it's not vacations time. ![]() |
|||
Posted: October 14, 2008 5:50 am | ||||
Lucato
![]() |
Hold on, let's forget the relief and get back to the hard work. :0) Ok, I have to agree that it would affect all these stufs, but I got another idea. Developers will be happy now, will want to kill me. Hehehe. Can't you guys generate a new version of the control 'Checbox ( 1 & 2 )' and keep the obsolete 'Checkbox ( 5 & 8 )' like you guys did with the 'Blend','Maximum Level', and 'Switch' (Obsolete components)? This way I think wouldn't affect any filter remmaped or not, and just the ones created with the new version of the checkbox control will make effect on the new filters created with it or the edited filter changed the controls and resubmitted to the library. What do you think now? |
|||
Posted: October 14, 2008 5:59 am | ||||
Vladimir Golovin
Administrator |
Interesting idea -- I'll run it through the devs.
|
|||
Posted: October 14, 2008 6:05 am | ||||
Vladimir Golovin
Administrator |
We've discussed it. The new way is problematic as well, because code-wise, remappers belong to inputs of receiving components, not to the control component. So, issuing a new version of the Checkbox component and obsoleting the old one won't help in this case.
|
|||
Posted: October 14, 2008 6:16 am | ||||
Lucato
![]() |
What a pity. I thought I had a solution Vlad. :0) I just didn't understand very well why we wouldn't we have a new control with 1 & 2 and get to use the remapp the same way, instead of thecheckbox as 33.3333 & 66.6666... Well, I can't argue once I have no programming knowledge. So, no overhaul. Ok, developers 1 x 0 for you. I'll be back with other stuffs in the future. hehehe. Thanks for your quick feedback Vlad. |
|||
Posted: October 14, 2008 6:38 am | ||||
Vladimir Golovin
Administrator |
It's not a matter of programming skill, but rather a matter of the current implementation of remappers. It could be either way, and our current implementation just happens to be the 'wrong' way for this particular problem. |
|||
Posted: October 14, 2008 6:55 am | ||||
Crapadilla
![]() |
![]() ![]() --- Crapadilla says: "Damn you, stupid redundant feature requests!" ;) |
|||
Posted: October 14, 2008 2:47 pm | ||||
Vladimir Golovin
Administrator |
This is truth, I confirm ![]() But I still think we'll need to refactor it at some point anyway. ![]() (Runs for cover). |
|||
Posted: October 17, 2008 4:36 am | ||||
Redcap
![]() |
How about this thought, it will make both the users (Us) and the programmers (You) happy. Just change the default to 1 and 2 and don't worry about how it effects the filters. Most people who use switches already have a remap so that shouldn't effect the vast majority of filters, and then the authors of the filters (if their filters are effected) can simply resubmit their filters after they change it. If the author doesn't change their filter and the filter is Low Usage just huck the piece of garbage to the side of the road. Chances are no one will miss it.
So it makes the programmers job easy and puts some responsibility on the authors of filters. If we want our filters to stay "quality filters" we must update just a handful of filters. If we don't update our filters it is a pretty good guess that we just spammed the website with crappy filters that we hoped would get us a free copy of FF. ![]() |
|||
Posted: October 17, 2008 9:47 am | ||||
Kraellin
![]() |
red, you're forgetting the thousands of one filter that might already be out there. it's not that big of a deal to simply do the remapping manually. and once you've done one you simply clone from there. if it werent a big hassle for the coders, then fine, change it. but frankly, there are MUCH bigger fish to fry than this one that i'd much rather see the coders work on.
If wishes were horses... there'd be a whole lot of horse crap to clean up!
Craig |
|||
Posted: October 17, 2008 2:11 pm | ||||
Nidi |
Continuing Lucato's idea, is not possible to make this as a patch in the checkbox control itself, without changing the remappers? Let's say like changing the remapper defaults in the after bind event to the Switch, something like if 5 then 1 and if 8 then 2 or something.
Besides, changing the filters wouldn't be a big problem since all the data resides in ffxml files and i suppose the change can be done with some advanced text replacer that replaces the old values with the new ones on the files themselves. |
|||
Posted: October 20, 2008 8:38 am |
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
33,712 Registered Users
+18 new in 30 days!
153,537 Posts
+6 new in 7 days!
15,348 Topics
+72 new in year!
25 unregistered users.