bulia byak wrote:
On 10/3/07, Joshua A. Andler <joshua@...533...> wrote:
Agreed. However, you still can re-use them, it's just a little more time consuming now. When you want to change your gradients as you used to, you can click the "Edit" button on the gradient toolbar to do it via the dialog. That method does not auto-fork and updates all shared gradients on canvas from my testing. Unfortunately it lacks the simplicity and speed of the on-canvas gradient editing though.
Sorry to disappoint, but this button is also going to disappear when the Gradient Editor is purged. All I need to do for this is add a numeric control for stop position onto the toolbar.
No disappointment given the option mentioned below. I don't personally use the gradient editor and I only brought it up because I wondered if it would work around that forking.
I hate to ask for anything additional given your willingness to humor us power users, but, is there any chance you'd be willing to look into adding the "no repeat, repeat, & reflect" combobox from the F&S dialog to the toolbar as well? Or do you not feel it fits there?
Bulia, would it be possible for us to have a toggle button on the gradient toolbar that toggles auto-forking? Obviously we would default it to "on".
OK, for you power users :) I think I can easily add a toggle to never fork the gradient vectors. It should be easy as it's a change in a single place in the code. But, god forbid, it will NEVER be on the toolbar - we've had enough trouble with people turning on "gradient move" button on the Selector toolbar and forgetting about it, and then complaining about weird behavior. Somewhere deep in the prefs would be OK with me :)
You rock! I was going to suggest a preference as opposed to toggle button, for the reason you mentioned (I think those four buttons are responsible for the most commonly reported issues). But, I suggested the toggle for the sake of uniformity with the selector tool & the toggling of handles in the node tool. Thank you for accommodating our workflow!
-Josh