[Soc-2017-dev] vertex paint project - ply exporter

[Howard Trickey]

Hi Darshan,

I think it is OK to leave the current control-K behavior (just replacing
color).  If one wants to do something that respects blend modes, one can
always just make a big-radius brush and use non-occlude mode, right?  Right
now, one has the solid feeling that if you use control-K, you will get
exactly the specified color and people are used to that. Even the name
'fill' to me means change to the specified color, not blend with the
specified color.

Anyone else with any opinion on this, feel free to weigh in.


On Mon, Aug 14, 2017 at 11:47 PM Darshan kadu <darsh7807 at gmail.com> wrote:

> Hello, Mr. Howard,
>
> In post #92 the user is asking for fill with blend modes. I think the
> current working is proper. What do you think?
>
> Thank you.
>
> On Tue, Aug 8, 2017 at 10:50 PM, Howard Trickey <howard.trickey at gmail.com>
> wrote:
>
>> Hi Darshan,
>>
>> On Tue, Aug 8, 2017 at 12:00 PM Darshan kadu <darsh7807 at gmail.com> wrote:
>>
>>> Hello Mr. Howard,
>>>
>>> I am fixing the issues from the thread you can see them on my commits.
>>>
>>>
>> I should make another experimental build to make it easier for artists to
>> test your changes since the last build.  Maybe I'll do that tomorrow.
>>
>>
>>> Well, one user asked the new color layer should be default one but post
>>> #99 says that current functionality is better than default layer.
>>> What do you think which one is better here?
>>>
>>>
>> I wonder if other readers of this mail want to weigh in on this point?
>> For context, the question is: when you hit the + button to create a new
>> vertex layer, should it copy the colors from the current layer, or should
>> it make the colors all white?  Several users on the BA thread suggested
>> that the current behavior (copying) was "broken".  I can see that point of
>> view: usually a "+"-key functionality to create a new thing in Blender
>> creates a "blank" thing. E.g., new material gets diffuse white. But the
>> dissenting user says that now there is no way to copy an existing layer as
>> a starting point for a new layer (and that there is an easy key sequence to
>> set a new layer to all white if that's what you want). I can see that point
>> of view too.  The "right" solution would probably be to implement some kind
>> of "copy" & "paste" functions for vertex layers; but I wonder how often (if
>> ever?) this is needed?
>>
>> I lean to thinking that I agree with the users who felt the current
>> behavior was broken, and thus agree with your change.  But don't feel
>> strongly about this. If other mentors don't feel strongly, maybe Darshan
>> you should try to get consensus from more users on the BA thread about
>> which behavior they prefer?
>>
>>
>>
>>> From my proposal, only gradient feature is remaining, but instead of
>>> that I have done other features, and also at this stage, I should more
>>> focus on bugs and issues. So, it is fine if I don't do gradient feature?
>>>
>>
>> I think it is fine if you don't do a gradient feature. It was never clear
>> to me anyway how to give the user fine control over what a gradient when
>> brushed would do. The bake-from-material-to-vertex-colors solution provides
>> a workaround anyway.  You should focus on bugs and issues right now.
>>
>>
>>>
>>> Thank you.
>>>
>>
>> _______________________________________________
>> Soc-2017-dev mailing list
>> Soc-2017-dev at blender.org
>> https://lists.blender.org/mailman/listinfo/soc-2017-dev
>>
>> _______________________________________________
> Soc-2017-dev mailing list
> Soc-2017-dev at blender.org
> https://lists.blender.org/mailman/listinfo/soc-2017-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/soc-2017-dev/attachments/20170815/de7e8e0e/attachment.htm