<div class="gmail_quote">On Sun, May 29, 2011 at 6:08 AM, Silvio Heinrich <span dir="ltr"><<a href="mailto:plassy@web.de">plassy@web.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">On 05/29/2011 12:22 AM, David REVOY wrote:<br>
> Hi Silvio,<br>
><br>
> I disagree here with you. This actual behavior speedup a lot my workflow<br>
> here and usage with Krita.<br>
> <a href="http://david.revoy.free.fr/forums/krita/2011-05-28_krita-preset_deevad.zip" target="_blank">http://david.revoy.free.fr/forums/krita/2011-05-28_krita-preset_deevad.zip</a><br>
> I did this brushkit (link above) with taking advantage of it ; check the<br>
> HSY color airbrush, and dodge explosion brush ; the result is I can<br>
> build my preset and be sure about the result I will got after select<br>
> them to paint.<br>
><br>
> But I also understand your point of view even if I don't use it this<br>
> way. Anticipating multiple usage are the way of a good software ; and I<br>
> don't want to impose a way to do.<br>
> So, I would suggest to add a icon acting as a checkbox in the top tool<br>
> bar to 'lock' the opacity and blending mode. (<br>
> <a href="http://www.new-hampshire-locksmith.com/lock_icon2.gif" target="_blank">http://www.new-hampshire-locksmith.com/lock_icon2.gif</a> ) . If user 'lock'<br>
> the preset won't load global opacity and keep the active blending mode.<br>
> A design like this can make happy all the way to use it , imo. Say me<br>
> what you think about it.<br>
> Best regards,<br>
><br>
> -David<br>
<br>
</div>Hmm... ok :)<br>
I think you did misunderstand me.<br>
I think you just want to be able to save a blending mode to a preset,<br>
so that you don't have to set it manually every time.<br>
That is fine and I want this too.<br>
<br>
But there are various issues with the way it is done currently.<br>
<br>
1. A preset should be able to overwrite the global blending mode but<br>
only --> explicitly <--<br>
This means having an option in the preset editor where you can choose<br>
the blending mode<br>
you want to use for this preset.<br>
When this option is activated, the global blending mode will be overwritten<br>
by the blending mode from the preset (when the preset is loaded).<br>
If this option isn't activated, the global blending mode should not change.<br>
<br>
2. I see no reason why the global opacity should be saved to the preset<br>
since<br>
we now have a slider in the opacity option in the preset editor.<br>
It does exactly the same. The global opacity option is simply for<br>
changing the<br>
opacity quickly while you are painting, so that you don't have to open<br>
the preset editor<br>
every time. If you want to save the opacity, just change the opacity in<br>
the preset editor<br>
save it and let the global opacity at 100%.<br>
<br>
3. There is no user feedback what actually will be saved. Sven said that<br>
he saves the<br>
Mirroring options too... I mean these are also global options that<br>
normally affect all paintOps.<br>
This breaks the UI logic. For example. It would be the same if you go to the<br>
preferences, go to "Tablet Settings" and change something. Then you save<br>
a preset and the<br>
"Tablet Settings" will be saved to the preset and every time you load<br>
this preset the "Tablet Settings" will<br>
be changed. It should be obvious that this would be really confusing,<br>
since the tablet settings<br>
are considered to be global.<br>
<br>
4. I don't know exactly what Sven changed but it seems to be a bit<br>
fragile :P.<br>
Some of the presets you gave to me are not usable/broken (they have this<br>
red cross after loading).<br>
And there is this strangle behavior that when loading a preset that uses<br>
the "Wash" painting mode<br>
and then loading a preset for the color smudge brush the painting mode<br>
is not set back to "Built Up".<br>
But the color smudge brush doesn't work in "Wash" mode (this is why i<br>
didn't include this option).<br>
Ok, I will be fair. This could also be caused by the broken presets.<br>
A while ago I noticed some similar behavior. I think a broken preset can<br>
somehow mess up<br>
the internal state of the whole preset system.<br><br></blockquote><div><br>Definitely not fragile :) That is totally unrelated. The red x only shows that the brush referenced in that preset isn't installed,<br> <br>
</div></div>