| Age | Commit message (Collapse) | Author |
|---|
|
|
|
WM_operator_poll() could fail in cases WM_operator_name_call() would succeed because calling the operator would setup the context before calling poll.
this would result in python raising an invalid error or menu items being greyed out.
now python can also check with an operator context:
bpy.ops.object.editmode_toggle.poll('INVOKE_SCREEN')
|
|
working.
Patch by M.G. Kishalmi, thanks!
|
|
disabled.
|
|
obj moving
Comment from source...
/* re-calculating the frame positions means we loose our original transform if its not auto-keyed [#24451]
* this hack re-applies it, which is annoying, only alternatives are...
* - dont recalc paths.
* - have an object_handle_update() which gives is the new transform without touching the objects.
* - only recalc paths on auto-keying.
* - ED_objects_recalculate_paths could backup/restore transforms.
* - re-apply the transform which is simplest in this case. (2 lines below)
*/
Martin, if you think this workaround is unacceptable, then automatic recalculating of paths after transform should probably be disabled since it looses data on non transform un-keyed values.
|
|
fix included in report from Martijn Berger (mberger)
made some small changes.
- use ints rather then unsigned long for printing, values are not likely to be very large.
- CMake remove strict flags from collada build dir since I had warnings in the collada headers.
- added xml2 to collada libraries else I couldnt get collada building.
|
|
(but not me for some reason).
For now revert most of r32757.
|
|
the brush system matches the brush mode with the object mode, but this doesn't work for 2D image view paint.
since the poll() function doesnt have access to the context, for now just check if no paint modes are active, default to texture paint.
|
|
different from the group layer
* Object layer flag was set too soon for group duplication.
|
|
|
|
have no "No camera" warning
Improve camera checking and move it before starting render jobs
|
|
The scenes 'Render' is kept by blender while blender runs but the callbacks were not cleared when the render was done.
In this case the callback would reference a freed render job.
This isn't normally a problem because on re-rendering new callbacks are set, however the sequencer can render a previously rendered scene without setting up callbacks.
Simple fix is to to dummy callbacks applied onto the scenes 'Render' struct once its finished.
|
|
UnMapping the reversed NLA strips timing was incorrect.
|
|
|
|
axis=(...) attribute
the axis was being constantly re-initialized from the view.
|
|
|
|
also make a mistake on this check last commit.
|
|
|
|
Added extend option to lasso.
also...
- selecting bones wasn't checking their layer of if they were hidden in a number of places.
- fixed memory leak.
small unrealed changes
- added PBONE_VISIBLE macro
- renamed functions used for paint selectoin from *_tface to paintface_*. sine they no longer have anything todo with tface's.
- removed scanfill include from BLI_blenlib.h, this is only used in very few places and quite specific.
Noticed lasso select is broken for metaballs and face mask mode but this has been the case for a while, will look into it next.
|
|
|
|
python icon button call, enum from 818 down to 444.
- remove unused space image members
|
|
* This caused nearly all particles to leak through the collision surface if simulation subframes were used and the collision object was moving.
* In addition to fixing this I also did some more cleanup of the collision code and refined some of the comments.
|
|
|
|
initializers is a c99 feature.
|
|
|
|
|
|
- use first selected if non active (clears confusion since this isn't at all clear)
- dont take unselected into account when calculating connectivity, would mess up in many cases.
|
|
* Sampled Motion Blur Panel missed check for compatible engines, causing the panel to appear in Game Engine and Netrender as well.
|
|
Fixed multires_apply_smat to work properly with different current and
total subdivision levels.
|
|
|
|
Kuznetsov. Thank you!
This fixes [#24484] Right Hand Ctrl key none functional for snapping?
|
|
from Keith Astoria (kastoria)
|
|
armature deformed mesh.
|
|
|
|
If still fails, check & update Freetype (OS one or Blender's lib/).
|
|
|
|
from the 2.4 them but they were never in the 2.5 theme, so marked as BLANK
now.
|
|
|
|
Patch by Emil Brink, thanks!
|
|
with underscore, or were simply not set correctly after code copy/paste.
|
|
preset.py"
- Setting operator properties was broken because of bpy_types.py meta-classing (surprising this wasn't noticed before!)
- Presets now use a dialog with an OK button.
- Presets use a check function on the filename so invalid chars are replaced editing.
- Submit docs operator was broken.
|
|
also known as: broken multicam strip caused by other fix.
Calculated render_size where it belongs (within the glow effect) and
restored old functionality.
also: renamed render_size to preview_render_size at all relevant places,
where the naming wasn't used correctly.
Hopefully it's now a little bit more clear.
render_size := render size from scene (just rescales width/height)
preview_render_size := preview render size from sequencer preview,
controls the resolution and the use of sequencer proxy sources
|
|
This fixes a rather subtle seeking issue with ffmpeg and Sony
XDCAM-footage.
Problem is: MPEG2 streams within an MP4 container can contain a start
time - at several places. There is a starttime within the video
and audio streams and one within the container.
FFMpeg commandline tool only uses the container starttime and we used
the stream starttime.
The world would be a better place, if those two timestamps always match
up, since in XDCAM-footage those two starttimes differ in 4
frames - and the container has the right one.
We now always use the container start time as ffmpeg commandline tool
does (in the hope, that there is a good explaination for this and this
is the right thing(tm) to do).
I tested this also with HDV footage, which seems to work with the new
code, too.
Additional fix: disabled seek_by_bytes again, since it will only work
correctly, if ffmpeg guessed the HDV bitrate right (which it doesn't).
If you have seeking issues with HDV and have an older version of ffmpeg
installed, please upgrade, newer versions have some fixes in them.
|
|
anti-aliasing is selected
* FSA and motion blur can't work nicely together the way they're currently implemented, so I disabled this in the ui and code.
* FSA is used if both are selected.
* Also changed the name "Full Sample Motion Blur" to "Sampled Motion Blur" to avoid confusion with full sample anti-aliasing.
|
|
- added a readme so that it's easy to understand how to use the py files.
- fixed typos in the usage message.
|
|
flipping problems and enabled for pose bones.
|
|
>> Compile failure on windows platform (see ML for Errors).
SVN Revert of Revisions: 32805, 32804 and 32802
|
|
|
|
This fixes [#24474] Pressing <Shift Alt A> or clicking "Play Animation ... reverse = True" does not play animation backwards
|
|
- fixed this error 7 different functions (deform groups, uv layers & similar).
- support for numbers over 999.
- renamed splitIDname() to BLI_split_name_num(), moved to BLI_path_utils
|
