| Age | Commit message (Collapse) | Author |
|---|
|
indent.
also indent case's within the switch (we already did both of these almost everywhere)
|
|
|
|
own patch
|
|
by Pedro Riera (priera), Andrey Dubravin and parts rewritten by myself.
|
|
by Pedro Riera (priera), Andrey Dubravin, I also made some changes.
|
|
by Andrey Dubravin (daa)
|
|
|
|
|
|
|
|
|
|
- when an fcurve had no selected keyframes, a default fallback value was used which caused view-selected to include frame 1, even when no selected frames were there.
- the vertical axis was always reset, ideally we would center vertically too but the way this operator currently works we only know about the frame range,
now don't change the vertical scroll when viewing selected since it would always jump to the top of the screen (view-all still acts this way).
|
|
path, ideally this would work everywhere but it's a known limitation, no need
to print an error in the console each time it happens.
|
|
|
|
Animation
there was no feedback to the user about the current frame rendering, for longer renders this is no good.
|
|
Mostly, "weight groups" -> "vertex groups", and usual case/endpoints/typos/etc.
As a remainder, please read http://wiki.blender.org/index.php/Dev:Doc/CodeStyle#UI_Messages before writing UI messages!
|
|
previous fix for checking char arrays against NULL.
|
|
character. also remove some dead code (return directly after return).
|
|
|
|
with the lasso in some cases, will look into this after release.
|
|
view3d-select bone operators can use it and get matching selection behavior when entering editmode.
- specifically - write to the connected parents tipsel flag when setting the rootsel flag.
|
|
entering editmode.
|
|
BLI_strncpy_wchar_from_utf8.
Checked other usages of this function but they seem to be fine.
|
|
inconsistency between 2.67/2.68RC and previous versions
This was in fact really nasty bug, caused by multitex_nodes
function using global variable R (which is a copy of current
renderer). this variable is not initialized to anything
meaningful for until first rendering (preview or final)
happened.
Since multitex_nodes might be used outside of render pipeline,
made it so whether CM is on or off as an argument to functions
multitex_ext_safe and multitex_ext. Now multitex_nodes() is
only shall be used for stuff happening from render pipeline!
Also needed to make some changes to other places, so all the
usages of texture sampling knows for the fact whether CM is
on or off.
And one more change is related on behavior of dispalcement,
wave, warp, weightvg modifiers and smoke. They'll be always
using CM off since texture is used for influence, not for
color.
It's rather bigger patch, but it's mostly straightforward
changes, which we really need to be done.
Reviewed by Brecht, thanks!
|
|
Issue was caused by operator redo saving values for previous
inverted channels, meaning the same channels will be inverted
next time operator runs.
Don't think it's useful to save operator values here, since
you don;t have visual feedback about which channels were
inverted. So marked all this properties as SKIP_SAVE. Gives
much more predictable results.
|
|
tests still).
also don't decrement active indices below zero (also a problem in 2.67).
|
|
data, delete_customdata_layer was using layer data pointer to check weather to adjust index values (but both pointers can be NULL). Remove this code and do in customdata.c
|
|
|
|
- BLI_strncpy_wchar_from_utf8 wasn't NULL terminating the destination string, caused uninitialized memory use in BPY_python_start().
- BLI_strncpy_wchar_as_utf8 could write one byte past the buffer bounds.
|
|
select)
|
|
|
|
now use the active object first if its selected, this means when multiple instances are selected, using the active object gives a predictable outcome.
|
|
|
|
terminated.
|
|
in fact the problem was caused by own previous fix/improvement for a different case, now this works as follows...
- render uses last-saved name, falls back to 'untitled' in blend file path.
- non render uses id-name always, saves into dir of last-saved image, fall back to blend file path.
|
|
if statements and redundant initialization vars.
|
|
- boids random option was falling through to average.
- (NC_OBJECT | ND_DRAW) notifier was falling through to ND_SHADING button preview updates.
|
|
were falling through when its obviously incorrect to do so.
|
|
allocating.
|
|
BLI_testextensie_glob every time in the file selector with a blank string.
|
|
- BKE_mball_center_median(), didn't work.
- clip_refresh was removing handlers from wrong space.
- new_modifier, replace strcpy with BLI_strncpy
|
|
- reference to out of scope stack var
- freeing fixes size array (never allocated)
- add matching va_end for va_start
|
|
text threading issue.
|
|
buffer antialiasing that was restored in 2.67 after it was missing in the new
compositor implementation.
This option tends to make results worse rather then better for Cycles renders,
but is useful for Blender internal. Their Z-buffers look quite different for
antialiasing, and I'd rather not change either.
|
|
The problem was that when the camera is selected, the transform manipulator
is located exactly at the camera view location, and this was blocking selection
of other objects with some OpenGL implementations.
|
|
overrides
scene settings when pressing F12 over a 3D view.
|
|
disable editing a string on operator UI popups, causes feedback loop
|
|
This matrix was used to store the space the object is in,
which then was accessed by snapping code. No reason to
keep it as a global variable (which isn't safe for threading,
unlikely it'll give issues now, but it's easy to avoid
issues early here).
Now made it so BKE_object_where_is_calc_ex will get an
optional parameter originmat and set this matrix in
solve_parent.
Original patch by self, minor changes by Campbell, thanks!
|
|
Internally it was only invoke callback set for an
operator template. This invoke was setting such
properties as mouse_x and mouse_y and was calling
an exec function.
This meant that t seemed to be really easy to
use node.select operator from by giving a mouse
positions, but in fact it wasn't possible (because
it requires exec callback)
This commit sets operator's template exec callback,
which makes it possible using node.select from
python.
|
|
mousewheel value is now clamped too and raised the limit to 500.
|
|
armatures undo state now stores ID-properties.
|
