<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Yes! That's the one :)<br>
<br>
Cheers!<br>
<br>
-Andy<br>
<br>
<div class="moz-cite-prefix">On 08/11/2013 21:27, Jonathan
Williamson wrote:<br>
</div>
<blockquote
cite="mid:CAKGyzW7NsS1bFGvorRBpW8aBdYydKzmn9OQD0jv7n-1WeJZxwA@mail.gmail.com"
type="cite">
<div dir="ltr">Andy, are you thinking of Inset Extrude for the
interactivity? </div>
<div class="gmail_extra"><br clear="all">
<div>
<div dir="ltr">Jonathan Williamson
<div><a moz-do-not-send="true" href="http://cgcookie.com"
target="_blank">http://cgcookie.com</a></div>
</div>
</div>
<br>
<br>
<div class="gmail_quote">On Fri, Nov 8, 2013 at 3:25 PM,
metalliandy <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:metalliandy666@googlemail.com"
target="_blank">metalliandy666@googlemail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF"> Hey guys,<br>
<br>
I think the main requirement for a decent bevel is that by
default the result would be as even as possible with the
same angle & width being obtained wherever possible.
Hard surface modelling is made much harder by inconsistent
bevel widths so I would vode for the 'Along New Face'
option too.<br>
That being said current functionality should be retained
of course as flexibility is the key to robust modelling
tools. :)<br>
<br>
I would also like the interactive control handles in the
3d viewport from the old inset script to make a comeback
and be added to the bevel (and inset while we are at it ;)
), though the name of the addon alludes me atm. Perhaps
Jonathan remembers the one I mean? If not I will find it
out later and post it.<br>
<br>
For the naming I would use amount or percentage vs
fraction too. I think they would make much more sense to
artists in general. <br>
<br>
Cheers,<br>
<br>
-Andy
<div>
<div class="h5"><br>
<br>
<div>On 08/11/2013 19:54, Jonathan Williamson wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hey Howard,
<div><br>
</div>
<div>I think these options would be very valuable.
I know that in my work I would generally prefer
the <b>Along New Face </b>option. I also see
the <b>Along the Bisector </b>option to be
quite valuable for when you want to chamfer a
specific amount. </div>
<div><br>
</div>
<div>As for naming, I think <b>Amount </b>is a
better name. Offset to me means distance shifted
from center. Whereas while beveling what I care
about is the "amount of beveling". </div>
<div><br>
</div>
<div>Percentage is consistent with other areas of
Blender I believe, and so I suggest leaving that
as is. I don't know of anywhere that uses
"Fraction".</div>
<div><br>
</div>
<div>As for naming of the methods, I'm not sure. I
don't particularly like the existing naming, as
it doesn't clearly explain the method to me. But
I cannot currently think of a better
alternative. If I think of something I'll let
you know.</div>
</div>
<div class="gmail_extra"><br clear="all">
<div>
<div dir="ltr">Jonathan Williamson
<div><a moz-do-not-send="true"
href="http://cgcookie.com" target="_blank">http://cgcookie.com</a></div>
</div>
</div>
<br>
<br>
<div class="gmail_quote">On Fri, Nov 8, 2013 at
1:45 PM, Howard Trickey <span dir="ltr"><<a
moz-do-not-send="true"
href="mailto:howard.trickey@gmail.com"
target="_blank">howard.trickey@gmail.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0
0 0 .8ex;border-left:1px #ccc
solid;padding-left:1ex">
<div dir="ltr">I have now triaged and about to
attack the bevel bugs in tracker.
<div><br>
<div>A number of them are really feature
requests, in that they want an algorithm
that does something different than what
the bevel algorithm does today (and
there are reasons for why it does what
it does today). I'd like to start a
discussion of what bevel should really
do -- where it should change what it
does today, and where we should just add
more options.</div>
</div>
<div><br>
</div>
<div>E.g., see <a moz-do-not-send="true">https://projects.blender.org/tracker/index.php?func=detail&aid=34504&group_id=9&atid=498</a></div>
<div><br>
</div>
<div>A start of what will eventually become
the developer documentation for the bevel
code is here:</div>
<div><br>
</div>
<div><a moz-do-not-send="true">http://wiki.blender.org/index.php/User:Howardt/Bevel</a><br>
</div>
<div><br>
</div>
<div>This start is about how does one
measure the 'bevel amount' (currently
called 'offset' in the interface). Please
read. You can see that there are 4
alternatives, each with something to
recommend themselves. I propose (and have
already implemented, but not submitted)
giving all 4 options to the user, with
'Along Face' the default.</div>
<div><br>
</div>
<div>Questions for this list:</div>
<div>- Is this a good idea? Should I submit
it?</div>
<div>- Are there better names for the
methods?</div>
<div>- Should I change the name 'offset' in
the interface to something else ('amount',
maybe?); it would be kind of annoying to
change the code at this point, since the
field persisted in .blends is called
'offset'.</div>
<div>- Should 'Percentage' perhaps be
'Fraction'? I don't remember what is
common in Blender, to enter such numbers
as between 0 and 100, or between 0.0 and
1.0. One problem with leaving it as
Percentage is that the numbers are way out
of range with the numbers used for the
other three methods, and I probably have
to figure out how to scale the interactive
number differently when Percentage is
used. So I would prefer this to be
'Fraction'.</div>
<div><br>
</div>
<div>There are other questions about how to
deal with problems when all constraints
can't be met (when beveling several edges
together); and more about the algorithm
used to fill in rounded corners; I'll fill
in the discussion about those later.</div>
<span><font color="#888888">
<div><br>
</div>
<div>- Howard</div>
<div><br>
</div>
</font></span></div>
<br>
_______________________________________________<br>
Bf-modeling mailing list<br>
<a moz-do-not-send="true"
href="mailto:Bf-modeling@blender.org"
target="_blank">Bf-modeling@blender.org</a><br>
<a moz-do-not-send="true"
href="http://lists.blender.org/mailman/listinfo/bf-modeling"
target="_blank">http://lists.blender.org/mailman/listinfo/bf-modeling</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
Bf-modeling mailing list
<a moz-do-not-send="true" href="mailto:Bf-modeling@blender.org" target="_blank">Bf-modeling@blender.org</a>
<a moz-do-not-send="true" href="http://lists.blender.org/mailman/listinfo/bf-modeling" target="_blank">http://lists.blender.org/mailman/listinfo/bf-modeling</a>
</pre>
</blockquote>
<br>
</div>
</div>
</div>
<br>
_______________________________________________<br>
Bf-modeling mailing list<br>
<a moz-do-not-send="true"
href="mailto:Bf-modeling@blender.org">Bf-modeling@blender.org</a><br>
<a moz-do-not-send="true"
href="http://lists.blender.org/mailman/listinfo/bf-modeling"
target="_blank">http://lists.blender.org/mailman/listinfo/bf-modeling</a><br>
<br>
</blockquote>
</div>
<br>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Bf-modeling mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Bf-modeling@blender.org">Bf-modeling@blender.org</a>
<a class="moz-txt-link-freetext" href="http://lists.blender.org/mailman/listinfo/bf-modeling">http://lists.blender.org/mailman/listinfo/bf-modeling</a>
</pre>
</blockquote>
<br>
</body>
</html>