Age | Commit message (Collapse) | Author |
|
|
|
and instead return a new color.
also fix for error in last commit, the brushes alpha wasnt set for weight paint info struct.
|
|
- store brush_alpha() result so it doesnt need to be called for each vertex when paitning.
- use _pressure suffix rather then _final to show the pressure has been applied.
- weight paint was needlessly calculateing the test weight when multipaint was enabled.
|
|
function (was duplicated), also add enum for vpaint blend modes.
|
|
Things like brush size and strength accessors now take a scene
parameter rather than guessing about which Scene's unified paint
settings to use.
Setting the size/strength through RNA can now be done separately for
the brush or the UnifiedPaintSettings.
The UI python code required updating to check whether the
size/strength controls should use brush or UnifiedPaintSettings RNA.
Radial control also required some updates to switch between the two
RNA sources.
|
|
Another bunch of fixes for select keymaps (sequencer, node, nla, graph, action).
|
|
More "Reset ops properties" stuff, in select C keymaps this time.
Also ARMATURE_OT_select_inverse -> ARMATURE_OT_select_all(action='INVERT'). Left the select_inverse op code, though, it’s not using the same algo as INVERT of select_all ???
|
|
original verts weight).
was an error in own recent commit.
|
|
node editor node select)
caused by own use-last-settings, will be more of these, need to go over all keymaps.
|
|
use rgb_to_grayscale in more places.
|
|
|
|
|
|
since most callers need this too.
|
|
- minor change to FTOCHAR use.
|
|
brushes were doing curve lookups within this macro for example.
|
|
using keymap).
Yet I wonder how much of these remain (and why some, like e.g. selection in 3D views, did not have that problem)… This is a bit fuzzy, imho.
|
|
|
|
select_inverse operator.
|
|
invert option.
|
|
with last-settings, so texture translate doesn't apply to the grab key.
|
|
the right keys/handles.
|
|
or printing output.
|
|
shows changes in 3dview without having to exit + enter editmode.
|
|
|
|
|
|
change alpha of `Tick` in boolean option button).
|
|
animation and output is H264
Issue was caused by incorrectly set PTS value frames came form Scene strip renderer.
This value used to be calculated from RenderData current and start frame which
lead to non-uniformuly counting which totally confuses encoder.
Switch append_avi and append_ffmpeg to use current frame from rendering scene
(which was already passing to this functions and was used mostly for logging)
and start frame of rendering scene (it's new parameter added). This allowed to
calculate correct PTS value easily and get rid of global static sframe variable
in writeavi.c file.
|
|
draw with low alpha)
|
|
'dw_prev'
|
|
add some tips to the python docs.
|
|
center bones
normalize function simply wasn't called on the mirror vertex.
also fix 3 other bugs / inconsistencies
* when mirror is enabled, center verts get themselves as the mirror vertex, wpaint code didn't check for this case, mirroring the vertex to it self (would work, but unneeded).
* normalizing after painting would scale the active weight too, now keep the painted weight and adjust others when normalizing.
* VP_ONLYVGROUP wasn't respected for mirror (mirror vertex group would always be added).
|
|
to do_weight_paint_normalize_all(), just check before calling.
|
|
do_weight_paint_vertex(), no functional changes.
|
|
|
|
Added RNA for the unified paint setting flags that matches the Brush
RNA. Fixed the getter/setter functions to avoid guessing which Scene's
UnifiedPaintSetting to use. The getter functions take a Scene pointer
now, the setter functions are removed in favor of a more explicit
approach through RNA:
Rather than RNA choosing whether a property's value is in the Brush or
in the UnifiedPaintSettings, there are now explicit properties for
both. The UI code has been modified accordingly to switch the toggle
buttons between affecting the Brush and the UnifiedPaintSettings.
|
|
|
|
opengl rendering (previously was hard coded at 5).
|
|
There are also some changes that need to be done to libmv but I'm
leaving those out so I can get it patched upstream first.
(Only works with gcc/g++ if we want to use sun's compiler we would need
to get rid of all of our annonymous structs which I don't think
we want to do at this point, example:
typedef struct wmNDOFMotionData {
union {
float tvec[3]; // translation
struct { float tx, ty, tz; }; // this would need to be fixed
// something like this or something similar:
struct { float x, y, z; } t;
};
...
)
Kent
|
|
always correct.
|
|
|
|
|
|
|
|
annoying to have 'Reset' move objects to 0,0,0
|
|
defaults.
details
- uses redo stack to get recent settings from.
- adds a flag to IDProperties so RNA_property_is_set() can return false even if the property is exists.
- PROP_SKIP_SAVE option skips these settings from getting reset (as with presets).
|
|
to add a second version of the function which takes the property rather then its name.
|
|
string functions in more places too.
|
|
fix for sequencer unique naming which was missed with string length update.
|
|
- use more logical names for strings, noticed too many strings called `str` when reviewing name patch.
- pass __func__ macro to uiBeginBlock(), quite a few names were wrong (copy/paste error).
|
|
This commit extends limit of ID and objects to 64 (it means 63 meaning
characters and 1 for zero-terminator). CustomData layers names are also
extended.
Changed DNA structures and all places where length constants were hardcoded.
All names which are "generating" from ID block should be limited by MAX_ID_NAME-2,
all non-id names now has got own define called MAX_NAME which should be used all
over for non-id names to make further name migration stuff easier.
All name fields in DNA now have comment with constant which corresponds to
hardcoded numeric value which should make it easier to further update this
limits or even switch to non-hardcoded values in DNA.
Special thanks to Campbell who helped figuring out some issues and helped a lot
in finding all cases where hardcoded valued were still used in code.
Both of forwards and backwards compatibility is stored with blender versions newer
than January 5, 2011. Older versions had issue with placing null-terminator to
DNA strings on file load which will lead to some unpredictable behavior or even
crashes.
|
|
bug was introduced with cycles merge.
|