Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
only when deleting the last color.
|
|
* Remove some duplication in deletion code
* Fix crash when restoring file from last saved state.
|
|
Avoid having an invalid active index if user deletes a color.
Also attempt to set active color on clicking (Not working yet but fix
coming soon)
|
|
|
|
Logic for load/reload was duplicated, Fix T28087 missed reload.
De-duplicate, also replace stat -> BLI_stat
|
|
|
|
|
|
Fix alpha under equation according to porter-duff and user docs that
state that effect should invert he order of channels and reduce to alpha
over when factor is 1.0.
BTW, we don't really expose any factor here...lost feature from 2.49?
|
|
|
|
|
|
No need to copy/restore entire object struct (just to read location)
|
|
also add operator to test blacklist
|
|
- clamp selection on entering editmode (Python may have changed).
- BKE_vfont_select_get no longer succeeds with an empty selection
this caused many operators to go ahead and operate on zero size array.
|
|
Failed on any cyclic poly line.
|
|
|
|
|
|
Core of the issue is that pointcache handling in depsgraph were (re-) tagging
for update some objects on hidden layers, when all their dependencies remained
untag.
Since we do not want to update objects on hidden layers, take this data into account
when flushing pointcache.
Investigations and org patch by self, reviews, advices and final patch by sergey, many thanks! :)
|
|
|
|
This was never implemented, actually... Was also the occasion to rework a bit
`curve_deform_verts()`, code there was sometimes needlessly complicated and slowish
(like getting weight from dm vertex per vertex, instead of whole array at once...).
|
|
The problem was it used copied verts on the opposite side.
|
|
Issue noted in T35952, now if you convert a free handle to an aligned handle,
it will move the selected handle.
|
|
|
|
Free draw objects instead of tagging object update and doing
recalculation of derived meshes. The reason is that if user deletes all
slots and tries to paint, the system will invalidate the cached in
projection painting derivedmesh. This will promptly crash. Invalidating
the draw objects only is also much cheaper.
|
|
Bring back shading in texture painting.
This works now but it uses 3 texture units instead of two. Most GPUs of
DirectX 8 (OpenGL 1.4 should cover that) functionality even should have
those, but some old GPUs might not work with that. In any case, I hope
we will be moving to OpenGL 2.1 requirement soon anyway where 4-8
texture units are usually the norm.
|
|
- Drawing grease pencil fail without scene-lock.
- Converting to curve failed without scene-lock.
- Outliner drag into viewport failed with local-view.
|
|
|
|
- lamp
- camera
- font
- empty & effector
Also fix inconsistency with apply transform
(modified shape-keys for meshes but not curve/lattice)
|
|
Typo in material localization code.
|
|
Color ramps with no handles caused issues.
|
|
|
|
|
|
|
|
Missed that part of the report somehow, thought it's all about world..
|
|
Include explicit control for texturing:
This commit introduces a painting mode option, available in
the slots panel. The default value "Material" will create slots from the
blender material, same as just merged from the paint branch.
The new option "Image", will use an explicit image field that artists can use
to select the image to paint on. This will should allow painting regardless
of the renderer used or for use in modifiers.
|
|
* Add ability to choose blend type and enable/disable toggle for each
slot for blender internal.
|
|
The issue was caused by the world localization setting the ID_WORLD
type update tag. Now using a function which doesn't pollute the library
and which doesn't set update flags.
|
|
Also avoid looping over all objects for texture paint checks when a
material changes, only check active object.
|
|
|
|
internal.
This should eliminate some confusion when people use external render
engines.
|
|
|
|
|
|
Files older than rB37e1285 have broken hair sim due to the (hacky)
velocity "damping" factor, which is not initialized to 1.
|
|
unit.c intentionally doesn't include DNA or BKE headers (except its own)
|
|
|
|
assumes translations are in meters.
Turned out there were several issues in handling of scale parameter by numinput.
Fixed that by factorizing more some code in common with 'usual' numbuttons eval code
(new `bUnit_getScaleUnit()` helper will return valid scaled value, depending on
given system and type).
Now, numinput behaves as expected - using default unit amended by scale in case no unit is given
(i.e. entering '20' with a scale of 0.01 will give you 20cm, and '20cm' as well!).
|
|
|
|
for (only) negative number n, and sets to frame n for non-negative number n.
This appeared in rBrB94cb20ff4e78b, purposedly it seems, but without even
a single line of comment to explain why this was needed. For now, remove it.
|