| Age | Commit message (Collapse) | Author |
|---|
|
* Removed outdated properties from the presets.
Note: it does not fail anymore, but needs an update for new settings probably.
|
|
|
|
|
|
Only mysterious courant from bpy.types.ParticleSettings.courant_target reamins...
|
|
|
|
1. first pass only fast nodes are calculated and only to the active
viewer node
2. second pass all nodes to all outputs
Temp disabled highlights because of random crashes.
|
|
|
|
|
|
normalise->normalize).
|
|
|
|
pieces of code using mis-spelled names).
|
|
|
|
|
|
|
|
* Elbeem exporter code now overrides user settings to No Slip in case the object is animated;
* UI of fluid obstacles now disables slip settings when export animated is enabled;
* Added in this later option's tooltip a mention that it enforces No Slip!
|
|
|
|
object panel when the blend file has naming collisions with library data.
also minor style cleanup in bpy_rna.c
|
|
Should also fix the broken py ops tips...
|
|
covers all cases...
Will run a complete test case tomorrow, regexes killed me this evening!
|
|
it available for future "UI Translation" addon, and probably other UI-related tools as well.
Notes:
* This is a somewhat reworked version of what is currently in bf-translation's trunk/po/tools, not yet fully functionnal (well, 95% is ;) ) nor fully tested. ultimately, it will replace it (being "svn-linked" in bf-translation).
* Added feature: more complete/strict tests (yet some work to be done here).
* Added spell checking (huge spellcheck commit incomming...).
* Trying to get rid of xgettext itself (should e.g. allow us to use #defines as contexts, among other things...). But currently captures less strings, work needed here too.
Please note this includes libfribidi.dll, as it is hard to find it for windows (unixes should have no problems here).
|
|
|
|
|
|
|
|
useful for doing ray casts from the view.
|
|
descriptions.
|
|
|
|
The transform operators in nodes will now use the unselected nodes to generate snapping points. Unlike object snapping, node snapping works for the x/y axes separately and snaps node borders to same borders of unselected nodes. The sensitive area for node borders extends over the whole view2D range, to enable simple alignment of nodes in both x and y direction.
For snap points in the node editor an additional enum value is stored to indicate the type of node border (left/right/top/bottom). This works as a constraint on possible node alignments: only same border types align with each other.
|
|
UV Coords" (which isn't a bug at all).
The tool works OK, except it was messing vertices' order of polys, often giving ugly results! Now only using sorted list of vertices indices to find matching polys.
|
|
write presets there but not show up in the menu.
|
|
|
|
Snapping actually was working already, but grid spacing was set to 1.0, which is basically pixel size in the node editor. Increased this to 1x grid step for fine snapping and 5x grid step for rough snapping.
Grid drawing in node editor now draws 2 levels in slightly different shades to indicate the different snapping modes better.
Node editor also supports the general use_snap tool setting to enable automatic snapping during transform. For now only the incremental snapping is supported, in future could be extended to enable alignment between nodes in a number of ways.
|
|
|
|
|
|
|
|
date versions
|
|
key data.
useful if you add many keys to one part of a curve, then later want to key another part - but dont want to continuously make the same corrections.
|
|
* Fixes for the "Back to Black" theme, patch by meta-androcto. Fixed text editor select & vert edge select color. Thanks!
|
|
Problem was py code of main texture panel was not doing any check on the pinned id, assuming it managed the textures itself - but this is not the case of the Object datablock...
All work actually done by Sergey, was just missing the Lamp specific case. Checked both in code and with tests, quite sure all cases are now correctly handled!
|
|
reported by Mikko-Pentti Eronen.
Near sensors only pick up "actors," but objects with character physics did not have the actor option displayed. By setting the character physics object to actor, it can be picked up by the near sensor. However, it collides with the near sensor, which sounds like bug [#31701]
|
|
Issue was caused by some stuff happenign in wm_operator_finish() which uses
to somehow restore changes made by transformation invoke function.
Solved by not calling translation operator directly from duplication operator
(which is in fact really tricky) and use macros instead. This macros calls
duplication operator which simply duplicates strip, and then calls translation
operator.
|
|
|
|
the one brush and switch blending options.
|
|
C, D - in initial message.
|
|
|
|
Patch by Philipp Oeser (lichtwerk), just did style change (better to not define a value twice, so only affecting the three color components, not the alpha, also using the slice syntax makes things much more compact ;) ), thanks!
|
|
Patch by Philipp Oeser, thanks!
|
|
|
|
viewport option.
|
|
|
|
|
