| Age | Commit message (Collapse) | Author |
|---|
|
This change means that when going from having no FCurves active to having
an active FCurve, the properties panels will not get stuck with only showing
the "View" tab, which is not that useful a lot of the time.
|
|
Gives a bit better precision than creating a line in some cases,
use for ED_view3d_win_to_3d.
|
|
|
|
Sync selection option made adding a new UV layer select all edit-mesh faces.
Now just select the UV's, ignoring sync-select option.
|
|
There was already an attempt to do it, but it worked incorrect because
of wrong recursion check.
|
|
|
|
This patch depends on D1747, which upgrades the Recast version. It exposes the new Recast partitioning methods in the navmesh generation.
Reviewers: campbellbarton, moguri
Reviewed By: moguri
Projects: #bf_blender
Differential Revision: https://developer.blender.org/D1748
|
|
The version of Recast that Blender ships with is from 2009. This patch updates the Recast version to the latest version, 1.5.0. The Detour version remains untouched.
Reviewers: campbellbarton, moguri
Reviewed By: moguri
Projects: #bf_blender
Differential Revision: https://developer.blender.org/D1747
|
|
This reverts commit d91316dc672dc1ee69fbd24d2f00124a24b75c6b.
|
|
Note that we may want to review that some day, we have quite a bit of ID types here that are
'blend file' view only, might be worth splitting the check based on this.
|
|
This is an attempt to fix report T47991.
|
|
|
|
Ctrl-LMB ignored 2D constraint
|
|
|
|
Project the point onto the 2d place where possible.
|
|
|
|
The improved Hosek / Wilkie model was added during my GSoC 2013 and the default since then.
The older model was kinda kept for compatibility, but after more than 2 years it's time to remove it.
The Hosek / Wilkie model is more realistic anyway, and people who really want a day / night transition can mix the Sky Shader with another one (e.g. color) and fade between the two.
|
|
|
|
|
|
active index was not reset to 'nothing' in case actual active item was filtered out.
|
|
For now leave precision at half a pixel until we have real fix.
Resolves T48023.
|
|
Rewrote to work with ngons and and more complex topology, now uses separate function.
Fixes T48009.
|
|
in uv panels (t, n)
Epic fail in recent rB2c3985 :/
To be backported to 2.77a!
|
|
only goes from the index value down, instead of keying all
|
|
|
|
|
|
|
|
Also added NULL-checks for RNA paths, though they might be a bit paranoid.
|
|
Would return OPERATOR_RUNNING_MODAL for non-modal operator.
|
|
Regression in d5f1b9c22,
threading deadlock rendering a scene from the OpenGL preview.
|
|
|
|
|
|
This option selects all paths between source/destination which are no longer than the path found.
Handy for selecting meshes with a grid-topology.
|
|
|
|
While this didn't show up as a bug, the center2d was being calculated with a zero aspect,
causing TransInfo.center2d to be NAN.
|
|
As noted by Antonio and Daniel, performing smoothing on the pressure values
for new strokes doesn't work that great. From an artist POV, it is apparently
"very strange that line thickness shrink suddenly after drawing it".
|
|
mapping behaviours (modal vs manual)
|
|
From T33052 by Harley Acheson (harley)
|
|
* This includes the "manually create" modes, which correspond to the previous behaviour
for setting up drivers. This is necessary when the current screen layout is not
well suited to having multiple property editors open (e.g. small screen or heavily
subdivided screen).
* Only the modes relevant for the current property type (i.e. array vs single)
will be shown
* The "Add Driver" entries in the RMB context menu have now been replaced by a
submenu which will list all the available mapping types.
* NOTE: The code for the ANIM_OT_button_driver_add() operator is perhaps a bit hairy.
However, it currently allows us to have the desired behaviour. It can always get
cleaned up later though.
|
|
from non-3DView region
|
|
Caused by rBc24be7ec6e5.
Before rBc24be7ec6e5, wm_handlers_do always called handlers a second time with event value KM_PRESS in case of a double click. After it, this was only the case for non-LEFTMOUSE events.
Since ui_popup_handler (almost) always returned WM_UI_HANDLER_BREAK, the second handler iteration with KM_PRESS wouldn't run. This fix just makes sure we return WM_UI_HANDLER_CONTINUE for double click events instead (causing second iteration to run).
|
|
Increment the seed on each use,
otherwise calling again selects the same order, unless you manually adjust the seed.
|
|
This operator is intended to be used by drag-n-drop, no user invocation
is expected to happen here. Use Add->Search to quickly add nodes instead.
|
|
|
|
make it easier to navigate
|
|
|
|
This never really worked that well, and often ended up being far too strong
to be of practical use. The new options do similar things, but with greater
control, so removing this old method now.
|
|
On second thought, these might be better names for these... I'm still not 100%
happy with these, but they will do for now.
(Best results currently seem to be with smooth 0.7, and subdivision steps 1 or 2)
|
|
exceeds GP_STROKE_BUFFER_MAX
Assuming that this subdivision + smoothing mostly only happens at the end of a stroke
anyway, enforcing this max-points limit in some cases was resulting in strokes that
weren't quite getting subdivided properly as the others.
|
|
|
