Commit Graph

1373 Commits

Author SHA1 Message Date
c36f20a7d2 style cleanup 2013-03-08 04:00:06 +00:00
dfa8540cdf use bool for rna funcs. 2013-03-07 02:44:55 +00:00
0d5b028d43 patch [#34103] use boolean in path functions and add comments.
path_util_1.patch from Lawrence D'Oliveiro (ldo)
2013-03-04 19:27:51 +00:00
9b5edeb881 code cleanup: view3d_clipping_test was making a vector copy for no reason. 2013-03-04 07:15:09 +00:00
4f4e45540d fix for harmless glitch rotating the camera in camera mode, having the center point so close to the viewpoint caused the helper line to erratically move about because of float precision. 2013-02-28 11:29:27 +00:00
2afca3e317 fix [#34426] Manipulator handles drawn incorrectly by depth
original patch by Philipp Oeser (lichtwerk) with own changes.
2013-02-28 06:12:06 +00:00
98f7f73644 fix [#34415] Edge slide results in segmentation fault on certain mesh 2013-02-26 03:20:10 +00:00
8d1f84d4b6 rigidbody: Don't set object to rigid body on dummy transform
Fixes [#34420] rigid objects not resetting original properly after running a simulation.
2013-02-25 22:36:50 +00:00
b1543f07bf Another bunch of UI translation fixes, thanks to Leon Cheung, Gabriel Gazzán and S. Lockal for spotting them! 2013-02-24 15:40:28 +00:00
20220d47e3 Dependency Graph: some refactoring which should have no user visible impact
besides performance in some cases.

* DAG_scene_sort is now removed and replaced by DAG_relations_tag_update in
  most cases. This will clear the dependency graph, and only rebuild it right
  before it's needed again when the scene is re-evaluated.

  This is done because DAG_scene_sort is slow when called many times from
  python operators. Further the scene argument is not needed because most
  operations can potentially affect more than the current scene.

* DAG_scene_relations_update will now rebuild the dependency graph if it's not
  there yet, and DAG_scene_relations_rebuild will force a rebuild for the rare
  cases that need it.

* Remove various places where ob->recalc was set manually. This should go
  through DAG_id_tag_update() in nearly all cases instead since this is now
  a fast operation. Also removed DAG_ids_flush_update that goes along with
  such manual tagging of ob->recalc.
2013-02-21 19:33:04 +00:00
5d04d06d76 Fix drawing of translated strings (can't use _ascii version of BLF_draw in these cases, when WITH_INTERNATIONAL is defined we need unicode support). 2013-02-20 08:39:31 +00:00
6adb526f31 change to proportional editing suggested by Jeroen Hoolmans,
don't interpolate projection, just project all points within the PET radius.
2013-02-20 00:44:18 +00:00
3d41532554 fix [#34244] Snap to face projection - Entire mesh is affected by projection when Proportional Editing mode is active, regardless of influence radius 2013-02-19 16:57:04 +00:00
04d628a5b5 Another huge bunch of new UI translations (some reported by Leon Cheung, thanks!)... 2013-02-19 15:45:56 +00:00
c5e6a35e85 Remove ztrans_hack. Looks like just keeping the angles compatible works well
enough.
2013-02-19 10:10:09 +00:00
c68d5325d0 fix for [#34283] wasn't working in my tests (attached to original report),
made bone roll get compatible angle values with the original roll.
2013-02-19 04:37:28 +00:00
926e0e7eb7 Bugfix [#34283] armature bones losing their roll setting upon translation in
edit mode

My earlier fix for [#33974] (in r.54061) was causing some problems where
manually specified roll values on horizontal or angled bones were getting reset.
This could be nasty as you might not notice the changes for a while (especially
when using stick bones without axes displayed).

I've now put in place a hacky compromise solution which should catch both of
these situations nicely. For z-axis (i.e. vertical) movements, the r.54061 fix
is used, while for everything else (moving or just touch-n-go), the old setting
is used.
2013-02-19 03:26:18 +00:00
098e4234b1 minor change to own recent commit with transform fcurve centers and some style edits and typo corrections. 2013-02-19 02:30:02 +00:00
9ab3d4ff1e fix [#34303] Rotation fcurves don't work with transforming with individual centers 2013-02-18 16:35:13 +00:00
4cd487d731 checking for V3D_LOCAL was duplicated in transform.c, and both checks not quite correct.
- When checking edimode, make sure its mesh editmode.
- Graph editor supports this option but wasn't being checked.
2013-02-18 15:47:13 +00:00
b0a7370284 vertex slide: dont write clamped value back into TransInfo.values,
this meant toggling clamp didn't take any effect until the mouse was moved. (annoying glitch)
2013-02-17 05:58:18 +00:00
18f12c3fa4 allow alt or Ckey to toggle clamping for vertex slide. 2013-02-17 05:39:55 +00:00
8d339a89db fix [#33949] T_ALT_TRANSFORM conflicts with "emulate 3 button mouse"
finally last transform tool relying on alt has an alternative.

Sequencer slide which makes room for the placed strip by moving others - Pressing G a second time toggles this behavior.
2013-02-14 14:50:16 +00:00
9449866bdc fix (for one case of...) [#33949] T_ALT_TRANSFORM conflicts with "emulate 3 button mouse"
ShrinkFatten operator now uses scale key to toggle 'Even thickness' option.
With the default keymap this is Alt+S,S.

Added functionality so the header print can get the key used for the modal keymap, some other operators should make use of this too.
2013-02-14 14:01:02 +00:00
b2feb19c02 fix for memory leak in transform when changing transform modes within transform
(if you held down the R-key for example).
2013-02-11 02:06:19 +00:00
b59ba34c37 fix [#34152] Vertex Slide - misleading description
also use C key to toggle clamping rather then alt (reported in [#33949]).
2013-02-11 01:55:58 +00:00
441c7fb79a fix for crashes running some operators in background mode and some divide by zero errors. 2013-02-06 02:48:03 +00:00
415b425e65 improve edge slide with ngon's, distance calculation was average edge length.
now use the slide vector to find opposite ngon edge which sets the slide destination.
2013-02-03 07:26:58 +00:00
1f21efdeac fix [#34073] Combined EdgeLoop slides weirdly on even try
concave check on co-linear edges could fail, avoid by using the loop-direction + face normal.
2013-02-03 06:09:29 +00:00
ae4db7eb59 Bugfix: "Extend" transform tool would leave dangling "temp meta strips" if none
of those strips occurred on the same side of CFRA indicator as the mouse
2013-02-02 05:38:57 +00:00
518bfbb1c9 style cleanup 2013-02-02 04:58:03 +00:00
c734808fb0 fix error with flipped vertex slide failing, also fix bug where you could be flipped and in proportional vertex slide mode. 2013-01-31 22:18:37 +00:00
340845289b fix [#34024] delete - Edge loop crash 2013-01-29 08:19:23 +00:00
0d0dc37aee tweak to edge slide - use a quads opposite vertex when both edges share a quad, gives nicer results. 2013-01-29 05:30:39 +00:00
e9a4dd202e fix for fix, ugh!, vertex slide with concave/convex ngons & normal flipping should now work properly in all cases.
... somehow I managed to make test-cases that worked in previous commits but failed in other cases.
2013-01-29 05:18:30 +00:00
69585591d6 Correct fix for r54164, the testcase I was using worked but different edge slide examples didn't.
Edge slide needed to check for concave ngons too.

add BM_loop_is_convex() and expose to python too.
2013-01-29 03:25:47 +00:00
c16a4ca84a fix for r54166, the average edge length needs to be maintained. 2013-01-29 02:17:19 +00:00
3b45518080 minor improvement to edge slide, normalize the edge vectors that accumulate the direction, otherwise longer edges would skew the direction. 2013-01-29 01:37:04 +00:00
3fc5002a4a code cleanup: add some comments about to get_next_loop() for edge slide, also name vars better (was using meaningless names). 2013-01-29 01:31:42 +00:00
a0bd829637 fix for edge slide bug, when there were no edges to slide along the direction calculated from the face would be wrong half the time (depending on the edge loop direction which is arbitrary). 2013-01-29 01:23:33 +00:00
af70a34bfb code cleanup: just variable naming 2013-01-29 01:02:45 +00:00
cf94722380 code cleanup: var rename and add assert, when writing to out of bounds array.
minor edit to recent tip change.
2013-01-29 00:20:04 +00:00
d4366b6f82 Bugfix [#34019] Limit Constraints still affected transforms when turned off
Limit Constraints (i.e. Limit Location/Rotation/Scale/Distance) with 'For
Transform' option enabled would still be applied when transforming objects even
when they were turned off using the eye icon in the constraint panel headers.
The "off" flag was never added to the checks for muted or disabled constraints
to be skipped here.
2013-01-28 23:57:02 +00:00
69900035b3 fix for G,G causing vertex slide in UV/Image window, also comment unused defines/enums. 2013-01-24 08:49:40 +00:00
aea3545973 Bugfix [#33974] Bone roll flips 180 degrees when extruding bones vertically
For example, if you're making a chain of bones (e.g. for a spine) by extruding
the tip joint of an initial bone, the bone rolls would be: 0 (for the initial
bone), 180, -180, 180, -180, etc. This has the undesirable effect of causing
B-Bones to twist to match the roll values at the other end of the bone.

The fix here seems to improve the situation in this case: bone roll values don't
flip or change anymore (in fact, the bone axes stay perfectly aligned now, as
they should). It also doesn't seem to cause any problems in other common cases I
checked.
2013-01-24 02:52:03 +00:00
419ce840f9 rigidbody: Make rigid bodies kinematic during transformation
This allows moving rigid bodies on frame > startframe.
Also rigid bodies can now be picked up and trown around while the
simulation is running.

Note: There is a small glitch with cancelling tansform during simulation
but it's tricky to get rid of.

TODO: Avoid static-static collision warnings
2013-01-23 12:06:18 +00:00
8b8d4ba7ef sim: Remove "continue physics" code
This was left over from 2.4x days and is not used anymore.
Now simulations are always interactive.
2013-01-22 20:47:03 +00:00
bfa065f10c Bugfix [#33852] Scale of a strip in NLA is changed after moving it long distance
using numeric input

When using numeric input to move strips, the strip extent clamping code could
end up prematurely truncating one endpoint. This was because the clamping code
uses the values of the other end (e.g. end for start, and start for end) as one
of the limits on its allowable range to prevent inverted strips.

Now we just set these values twice - the first time, one of the endpoints may
still get truncated (while the other one will be able to go to its correct
value), then the second time both will get set correctly (and validated too).
2013-01-21 06:31:17 +00:00
aa6374dc0a fix for own error in vertex slide, isolated verts mixed with regular selection would crash. 2013-01-21 03:00:10 +00:00
38cee985bb code cleanup: style & warnings. 2013-01-21 02:30:40 +00:00