| Age | Commit message (Collapse) | Author |
|---|
|
- new (and temporary) directory addons_extern/ to store external projects addons
|
|
|
|
upwards too (BGE at least uses this).
|
|
not used like this much elsewhere in rna.
|
|
|
|
- open operator was incorrectly checking if the font path was set.
- rna ID editable check was also incorrect, checking the ID name rather then the filename.
- use define FO_BUILTIN_NAME rather then "<builtin>".
|
|
incorrectly.
- rotation and bone scaling with Durian feature 'Local Location' would fail to correctly translate the bone
because a different matrix is needed for translation and rotation.
|
|
with -Werror in their CMAKE_C_FLAGS_DEBUG (so all warnings give errors).
but external libs which we don't maintain & generated code will have -Werror removed.
This is GCC only, MSVC can be added easily.
|
|
object mode."
* Re-added code to draw loose edge
|
|
|
|
|
|
WITH_MOD_DECIMATE, renamed WITH_FLUID to WITH_MOD_FLUID
|
|
|
|
|
|
when it failed due to there being shape keys.
|
|
was inverted - Enabled by default but not a hinge.
this also matches 'use_inherit_scale'
|
|
recursive header search when not using msvc.
- uv layout export wasn't setting the default filename.
|
|
by cmake devs.
globbing vs explicit is discussed here.
http://www.cmake.org/pipermail/cmake/2008-December/025694.html
Practical implications are:
- developers need to keep CMakeLists.txt files up to date.
- Users wont get strange linking errors if they build after a file is added, since CMake detects CMakeLists.txt is modified and automatically reconfigure.
|
|
works!
Reported by Lluc Romaní Brasó
Some of my earlier changes to the modifier handling code accidently sent out new events for modifier keys when they where held down (repeat).
Also lay foundation for shift+numpad handling.
|
|
using Video Editing - Effect - Glow
|
|
exporter_framework).
|
|
_LARGESOURCE64_FILE defined for zlib to not throw errors.
|
|
duplicates.
|
|
|
|
assigned.
Reported in #blender.fi by Mats Holmberg
|
|
There was a slight discreptancy between the tail values calculated on the spline before the head was displaced for the "chain offset" option and after this operation. However, only the original version got set.
This small difference resulted in B-Bones thinking that the endpoints of the bones were in places that they were not in, hence causing the curly patterns observed in the report.
|
|
|
|
|
|
The bone option 'Local Location' (flag BONE_NO_LOCAL_LOCATION) makes the location apply differently so snap to cursor failed for pose bones.
|
|
|
|
- armature_mat_pose_to_bone() was missing axis-angle check.
- added loc_axisangle_size_to_mat4() for completeness.
- use 'const' prefix where possible in math rotation functions.
|
|
it also modified the input rotation value which isn't expected for these functions.
|
|
|
|
Assertion `boi->space_accounted' failed. [#656100]
reported on launchpad.
calling glClear(GL_COLOR_BUFFER_BIT); was crashing blender,
since this is only used to blank the window before its drawn, disable for opensource ATI drivers.
|
|
|
|
|
|
|
|
* This fix is really only a bandage, as the underlying issue is that sequencer preview render doesn't yet use the job system.
* The sequencer preview can start a full render of the scene, and this can collide with other preview/actual renders in many cases.
* Drawing the sequencer preview is now disabled when an other render is in progress, but the sequence preview rendering could have already been started before the other render, so this doesn't really fix anything.
* For now only OpenGL rendering can be used for the sequencer preview reliably until it's reimplemented using the job system.
* Using the job system in the future can handle the clashes between different renders properly and will give users a nice progress bar to indicate something is happening while the preview is recalculated.
|
|
ensure minimum mouse distance for sliding edge verts else it becomes unusable.
|
|
comment on class
|
|
Reported by Dennis Dillert
A bit clearer wording.
|
|
|
|
After discussions with Campbell regarding #24336 and #24309, we've decided to make this property for curves to only get set when an F-Curve explicitly animates it.
As a consequence...
- ALL OLD FILES using follow-path constraints that depended on this changed behaviour will currently need manual patching to add an appropriate F-Curve
- Ctrl-P (Parenting to Curves -> Follow Path option) will now automatically create such F-Curves mimicking the old behaviour so that creating camera-following-path setups still works smoothly.
- Directly adding a Follow Path constraint bypasses this, so you'll need to manually add such F-Curves if you need them.
The main problem with the old approach was that there were many cases in which curve data could get added but the ctime would be incorrect until a frame change (i.e. on render) flushed this.
|
|
|
|
work, keys A, D, R and F do not
|
|
Warning fixes.
|
|
|
|
Silence warnings
|
|
The problem is the opensource nvidia nouveau drivers are slow running glReadPixels(), was hanging on memcpy().
However for autodepth its not needed to update the entire 3D view depths, so added view3d_update_depths_rect() to get the depths for a smaller area.
|
|
Silence a warning.
|
