| Age | Commit message (Collapse) | Author |
|---|
|
spaces around operators, and so forth). Many thanks!
|
|
|
|
|
|
source/blender/freestyle files.
|
|
|
|
Reported by Bastien Montagne, thanks!
|
|
* Split and moved Cycles’ render layers panels into the render_layer
context as well (would be nice to hide this context when not needed,
e.g. with the BGE, but this is not so easy to do nicely...).
* Fixed some inconsistencies with trunk (probably due to svn merge
glitches) using r52858 as reference. Also recovered the missing
release/bin/blender-softwaregl file.
* A bunch of style code fixes in Blender's own code (not Freestyle
itself yet): line lengths, spaces around operators, block formatting,
headers, etc. In rna_linestyle.c, color_blend_items was replaced by
ramp_blend_items (exported from rna_material.c).
|
|
Congratulations to all trunk devs on the Blender 2.65 release!
|
|
Implemented forgotten Calculator classes from boost migration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
edges/verts outside the clip area but the geometry would still get cut
|
|
mouse line would reset to 0/0/0
a few areas that use ED_view3d_win_to_segment_clip() didnt take into account the case where the segment was filly clipped, some callers even needed the segment not to be clipped.
- added ED_view3d_win_to_segment()
- ED_view3d_win_to_segment_clip() now returns FALSE if the segment is totally clipped, but the start/ends of the line are not zero'd as they were before.
|
|
clipping against the object space bounds.
more fixes needed here but at least correct whats there.
also ensure clipping is initialized from the object before handling modal operator events.
|
|
|
|
the mouse. - snap, angle snap, midpoint snap.
|
|
text stepping when ctrl is held.
This adds back the problem that double-clicking on a single char wont select it. Double click selection may need its own logic.
|
|
Regression from r34115.
|
|
RNA subtype), since Freestyle internally use angles in radians.
A patch set by Bastien Montagne (many thanks!)
NOTICE FOR BRANCH USERS:
This commit may break line drawing settings of already saved Freestyle files.
All angles are now treated as radians instead of degrees, so collections of
angle values might be necessary in order to recover previous visual results.
Affected properties are:
- Crease Angle in the edge detection options
- Min 2D Angle in the 'Splitting' section of a line style
- Max 2D Angle in the 'Splitting' section of a line style
- 'orientation' parameter of the Calligraphy thickness modifier
- 'angle' parameter of the PerlinNoise1D geometry modifier
- 'angle' parameter of the PerlinNoise2D geometry modifier
- 'angle' parameter of the 2DTransform geometry modifier
|
|
|
|
bpy.ops.image.project_apply() only use local images.
|
|
duplifaces like blender internal.
|
|
Already since like 2.61 - when Array draw was added - drawing only shadow
in bottom of menus with bad looking corners.
|
|
sockets' operator, ctrl+h), newly enabled render passes will not show up in the Render Layers node. The SOCK_HIDDEN flag cancels out the SOCK_UNAVAIL flag in that case. Disable the SOCK_HIDDEN flag as well when showing new passes to avoid confusion.
|
|
Now it checks for "Not less then 4.3" because it doesnt have >= 4.3.
|
|
adding meshes were scaling the user input values so the distance on the button didnt relate to the scale of the object added.
Now use an invoke function that scales unset default values.
|
|
|
|
|
|
from Tobias Johansson (mutze)
with some minor edits (don't treat '!' as an operator - python centric)
|
|
*Remove WITH_MINGW64 option, automatically test for presence of __MINGW64__ definition instead to determine presence of MinGW32/64.
*Placeholder for LLVM libraries (Compiled locally but still crashing on render due to thread issue).
|
|
Patch contribution by Bastien Montagne, thanks!
|
|
(would use MEM_mallocN in one case but malloc in another). better use blenders MEM_mallocN for both.
|
|
|
|
|
|
bevel modifier was making zero area faces & edges that made scanfill fail (since it no longer removes doubles when filling ngons)
|
|
|
|
|
|
Really was caused by a previous bevel making
a two-edged face, which caused other faces to
be dropped when copying a bmesh.
The quadstrip code needed to be more careful
to avoid creating two-edge faces.
|
|
Seems to be from the very beginning here, not sure why nobody noticed this is wrong.
|
|
as render engine. Still missing is colors and texture slots, but that's too
tricky to fix this close to release.
|
|
- Blender/Python Addon Tutorial: a step by step guide on how to write an addon from scratch
- Blender/Python API Reference Usage: examples of how to use the API reference docs
Thanks to John Nyquist for editing these docs and giving feedback.
|
|
IK-Solver crashes Blender. No constraint is created for target in that case, just needed to add a check.
|
|
which only have one texture slot.
also quiet float/double warning.
|
|
This was a regression in svn rev52718 caused by the fact that we can not
free packet fun until we've finished all manipulation with decoded frame
since frame and packet could share same pointers.
For now restored old behavior of next_packet which seems to be well
tested and better not do bigger refactoring here so close to release.
Memory leak fixed by that revision was fixed by calling av_free_packet
just before avcodec_decode_video2 in cases we're at the end of file.
Tested with valgrind and could not see any memory leaks in ffmpeg
area.
|
|
This doesn't work nice currently and there's no simple workaround for this,
it'll require lots of statistics about cards and some further investigation
on supported combination of draw methods and multisamples supports.
For the release better be more stable and do not deliver dangerous option.
|
|
|
