Search results 1 - 20 of 97
First | Prev. | 12345 | Next | Last
Control Locks in V4???
... the parameter name would underline it and make the little triangle more apparent. After a click, a dropdown menu would appear, so there would be no need for explaining the commands to users because the menu will state them in plain text, e.g. "Lockrandomization" / "Unlock randomization" etc... But on the other hand, I currently foresee no per-parameter options other than those related to randomizationlock, so perhaps this approach would be wasteful and less clear for users.
Control Locks in V4???
...
Control locks should be per-filter, and only per-filter, IMO.
The randomizer settings affect randomization globally (i.e per-filter), and so should control locks. Conceptually, they're a part of the randomization system.
If you start storing control locks per-preset, then randomizer settings should also be stored on a per-preset basis. That would be overkill and unnecessary, IMO.
" [...] the control lock will definitely be adjustable by the user, not just the author. However, authors will be able to provide the ...
Control Locks in V4???
... locks are supposed to help users fine-tune the randomization, acting as a per-control on/off switch for the randomizer, do they not? That's all they do: influence randomization. Consequently there appears to be a strong logical connection between the randomizer and control locks. To me, control locks appear to be an extension of the randomization system.
While there is no strict logical reason that control locks must be per-filter just because randomizer settings are stored globally, there appears to be a conceptual ...
Control Locks in V4???
Author: Crapadilla. If per-preset randomizationlocks are actually implemented, then I'd strongly suggest introducing a new property to control components which completely disables randomization (without the user being able to change that state short of editing the filter itself).
It really really ...
Control Locks in V4???
Author: Crapadilla. My main gripe with the idea of per-preset randomizationlocks is the following: It's a clickfest for filter authors!
Imagine you're readying a filter for submission. Now, you've already created 20 great presets, but suddenly it occurs to you that one of your filter controls really should be randomization-locked....
Control Locks in V4???
Author: Crapadilla. "The new locking approach makes the Randomizer Settings dialog obsolete, so I'm thinking about killing it off entirely, and replacing it with a menu that would appear when you click the little button to the right of 'Next Variant'."
Sounds good. Some suggestions:
Quick Lock >
...
Control Locks in V4???
Author: Vladimir Golovin. The new locking approach makes the Randomizer Settings dialog obsolete, so I'm thinking about killing it off entirely, and replacing it with a menu that would appear when you click the little button to the right of 'Next Variant' (we'll remove the ellipsis icon and replace it with our ...
Control Locks in V4???
... clickfest of a usability fail. "
I agree with Crapadilla. Per-preset locks seems like overcomplicating something which is meant to make the user experience simpler and easier.
It's likely that in terms of workflow, a user might set their randomizerlocks, hit the randomizer a couple of times, and then move sideways between to other presets: either creating new ones or jumping to a new preset and repeating the process.
I'd vote for: keep it simple.
Also, IMHO, having the locks needing to ...
Control Locks in V4???
... preview/fine-tuning 'modes' would behave in a controllable fashion if the mode toggle could be locked fr om randomization. Some examples:
1. Synthetic Cubism (http://www.filterforge.com/filters/501.html) has a 'Palette View Mode' checkbox that should really be locked from randomization.
2. Wind Blur (http://www.filterforge.com/filters/4222.html) has a 'Show Mask' checkbox that puts the filter in mask display mode. Should also be locked from randomization.
Modification locks however appear to be of lim ited usefulness ...
Control Locks in V4???
... filter with the random button than affect the whole thing. Now as a user, I also pick filters up, but as much as I'm used to seeing how authors set stuff up, there are also times when I can't tell if that slider's doing something at one level or another. Randomizing those can mean my designs may go away so I'd lock them down but there's a likely chance of that controller being ignored because of its naming or whatever it may be. Blah blah. In short: per-preset locks just allows us to save some groups and patterns and that way it avoids users fr om hassling ...
Control Locks in V4???
Author: Crapadilla. What exactly would be the advantage of having randomizationlocks per-preset, I wonder. Because I really do not see any.
For what reason should some presets come with certain controls locked for randomization and others not? Why on earth would anybody want to have presets of the same filter behave differently when randomized? Where is the benefit of that?
In my opinion, implementing per-preset randomizationlocks would actually make randomization ...
*cough* CONTROL LOCKS!!! *uncough*
... instead of salt... :D ... :devil:
Dear Vlad,
You're the best, man!!! Love this program!!! I was thinking that maybe CONTROL LOCKS might be a HUGE help for users as well as authors... Given the number of controls on most filters, CONTROL LOCKS would make it 110% easier to use randomization to zero in on desired results...instead of having to remember settings and go back to change them each time you hit the randomization button. Further, CONTROL LOCKS would make it 110% more efficient to explore a filter in 'high' ramdomization ...
Control Locks in V4???
Author: Vladimir Golovin. inujima, If I understood you correctly, you are proposing a modification lock, not just a randomizationlock.
So, when a parameter is locked, it cannot be modified manually, it is not affected by randomization, and it is not affected by applying presets. A locked parameter has its control completely disabled / greyed out.
Of course, it has to be per-filter,...
Control Locks in V4???
... locks should be per-filter, and only per-filter, IMO.
The randomizer settings affect randomization globally (i.e per-filter), and so should control locks. Conceptually, they're a part of the randomization system.
If you start storing control locks per-preset, then randomizer settings should also be stored on a per-preset basis. That would be overkill and unnecessary, IMO. "
That was my first reaction when I thought about this. However, I'm not sure that storing locks per filter follows from the randomizer ...
Control Locks in V4???
... controls (Environment, Brightness and Saturation) will have their own separate locks.
On the main Settings tab, we'll likely make Size and Variation lockable as well, instead of having people toggle this in Randomizer Options.
I'm undecided about randomizing / locking the Seamless Tiling checkbox. On one hand, randomizing it doesn't make any sense, but on the other hand, having a single non-randomizable control is not very consistent.
Control Locks in V4???
Author: StevieJ. Please tell me there are going to be control locks for use in randomization in this release??? :|
CONTROL LOCKS!!!
Author: StevieJ. You're on V3 now and still no sign of control locks for use in randomization??? :?:
Top 3 Features Wanted!!!
Author: StevieJ. Like the little locks on controls in PS... When you hit the randomization button, all the controls that are "locked" do not change/randomize...so when you are zeroing in on desired results, you can keep those controls locked that you know are providing the desired direction of your wanted result...instead of trying to remember all the settings of all the controls that you do not ...
Loop component
... control locks are a must-have... "
I also like much cool features and are a great thing but I agree with you that control locks is a must too, as the user created folders are already confirmed to be included in FF 4.0, but not yet the control randomizerlocks
Control Locks in V4???
... I can (without clicking around) switch between those as well.
The catch is this. If that filter exists, I may want to randomize just the colors of my filter while keeping the pattern and noise settings the same. I may want to keep the colors but randomize both the pattern and the noise. So what if I had 20 controls for this filter? Per-Filter locks means that the locks would be there globally, therefore I'd have to go and manually lock stuff around to get what I want. Per-preset means all of that is saved, meaning I wouldn't have to manually lock stuff for specific needs.
So when I mentioned ...
Search results 1 - 20 of 97
First | Prev. | 12345 | Next | Last
Join Our Community!
Filter Forge has a thriving, vibrant, knowledgeable user community. Feel free to join us and have fun!
