| Age | Commit message (Collapse) | Author |
|---|
|
- copy now gets up to 6 decimal places
- copy and UI float button editing now strip zeros: 1.000 -> 1.0
|
|
|
|
|
|
to include a few more that gcc is using too.
|
|
from Lawrence D'Oliveiro (ldo)
notes from tracker:
use bool for return type from BLI_remlink_safe, necessitating including BLI_utildefines.h in BLI_listbase.h
get rid of duplicate BLI_insertlink, use BLI_insertlinkafter instead.
A few places which were using BLI_insertlinkafter (actually BLI_insertlink), when it would be simpler to use BLI_insertlinkbefore instead.
|
|
script.
|
|
SF_VERT_AVAILABLE
|
|
|
|
|
|
converted from shorts are not always exactly unit length.
|
|
this was really not nice logic to try to fit into an assert.
|
|
made bone roll get compatible angle values with the original roll.
|
|
white background color
|
|
The RNA path interpretor code was using a function to get the portion between quotes,
this function was not even checking if there *are* quotes at all! Causing bad
memory allocs or crashes.
|
|
cause bugs but turns out its not used,
ifdef'd it out but keep in the struct in BLI_mempool for now.
|
|
|
|
Blender's triangulator has been rescued :)
This commit fixes errors with concave holes inside polygons.
Simple explanation:
Blender "ScanFill" works by sorting vertices from top-left to bottom-right, and connecting
these vertices with a sorted list of edges they have.
The inner loop then goes over every vertex, its edges, and tries to make triangles by
checking vertices that are next in the list.
- if the triangle has points inside: it creates an edge to this vertex, and continues
- else: add new triangle.
Very simple, fast and efficient. But it needed one more check for the first step: it should
check every vertex inside the triangle, and pick the best vertex for an edge based on forming
the sharpest angle with the tested edge. That solves the case for concave holes.
Blender ScanFill was coded 20 years ago, and is an own invention. I wanted a triangulator that
just fills any collection of polygons, including with holes.
No idea if this was ever published in a paper!
|
|
some reports in the tracker show errors on bmesh iteration which could be caused by this.
|
|
|
|
Now we do simple triangulation and calculate signed area of triangles to
account for concave polygons.
This only works correct for planar polygons but gives better results
overall.
|
|
Fixes small precision problems.
|
|
side to be considered convex (as it did in last release).
this is needed so zero area faces be dealt with by beauty fill.
|
|
- update man page for new additions since last release.
- note that --start-console argument is windows only.
- correct own assertion in own recent commit.
|
|
clicking a pair chars would select 3 - one to the left).
|
|
a rotation axis.
make is_quad_convex_v2,3() check for ISECT_LINE_LINE_CROSS intersection (that the lines actually cross each other).
|
|
value as in-out, since this is a convention for existing matrix functions.
|
|
rotated close to 180 degrees and there were edges both below and above
the 180 degree threshhold. Separating and averaging the negative and
positive angles seems to solve the issue making the tool a bit more
robust ;)
|
|
|
|
|
|
calltips.
|
|
enough in some cases and would make beauty fill fail.
now rotate the coords before calculation.
|
|
|
|
code (just realized that flag value was wrong, probably own typo in a previous commit :/ ).
That "trick" was nice when introduced, but it became kind of a pita since we added translation contexts...
|
|
|
|
function with a null check, callers better check the ghash exists first.
|
|
|
|
|
|
and Gabriel Gazzán on ML, and lockal on IRC, thanks).
The problem is that, when HAVE__BOOL is not defined (as it is the case in scons currently), BLI_utildefines.h defines bool as a standard type. Was using signed char, which makes eg "bool foo = 1024" be false (overflow)! Especially nasty when using bitflags (think we have been lucky to not have worse bugs because of that)!
So changed fallback bool type to unsigned int.
|
|
|
|
array (utility function currently unused).
|
|
|
|
make sure its valid. also remove some commented code (more then one generation of bmesh old).
|
|
should now work properly in all cases.
... somehow I managed to make test-cases that worked in previous commits but failed in other cases.
|
|
|
|
|
|
POSIX.1-2001
This is useful for gcc which does not define sqrtf/powf/... functions with preprocessor and therefore always used sqrt/pow/...
Float functions are generally 20-50% faster than their equivalents for double type.
|
|
non-threadsafe usage of guarded allocator.
Also added small chunk of code to check consistency of begin/end
threaded malloc.
All this additional checks are commented and wouldn't affect on
builds, however found them helpful to troubleshoot issues so
decided to commit it to SVN.
|
|
caused issue in blender internal with recent fix.
|
|
mat4_decompose() is similar to mat4_to_loc_rot_size() but returns
rotation as quaternion.
mat4_to_loc_quat() just returns location and rotation without size.
|
|
|
