Revision 7016538 by Dalai Felinto June 27, 2012, 21:57 (GMT) |
bge.logic.keyboard.getClipboard() and .setClipboard methods the idea of using methods instead of attributes is to avoid users abusing of the system calls. Thanks Campbell Barton for reviewing and small corrections |
Revision a09feb7 by Campbell Barton June 27, 2012, 21:41 (GMT) |
option so operators can be executed with undo enabled (and redo). |
Revision d30c735 by Campbell Barton June 27, 2012, 19:28 (GMT) |
missed tiff using 150 dpi as default in previous commit, use a define now. |
Revision f57c1c8 by Nicholas Bishop June 27, 2012, 18:39 (GMT) |
Avoid adding overlapping triangles in convex hull Add an epsilon value to the point-outside-hull test, helps when some of the input vertices are nearly coplanar. Fixes bug [#31941] convex hull fails (and depends on vertex order when it shouldn't) http://projects.blender.org/tracker/index.php?func=detail&aid=31941&group_id=9&atid=498 |
Revision 3247899 by Campbell Barton June 27, 2012, 18:29 (GMT) |
style cleanup |
Revision 25a018f by Campbell Barton June 27, 2012, 18:11 (GMT) |
change default DPI for images to 72, aparently 150 gives issues with adobe apps (which is stupid but default value isnt so important). |
Revision 8f8d7f5 by Sergey Sharybin June 27, 2012, 18:10 (GMT) |
Clean-up and refactor of current OCIO integration - Cleaned up some files -- seems there were some wrongly resolved conflicts which resulted into duplicated code in space_image.py and some build configuration files. - Store all color space related data (such as display device, view transform and so) as strings, so it could easily be ported to new OCIO configuration files and it'll be much more portable between different configurations. This required adding some look-ups to RNA associated with such settings, but it's indeed the only way to do this. If it'll be figured out such look-ups causes performance issues it's possible to optimize this further using hash. So far it's only few elements in list to be looked up. - Added support of display device transformation from OCIO configuration files. Display device is setting per-window and different windows could have different display devices, so it's possible to have one blender window opened on sRGB monitor and another one on xyz projector. Display device is ignored when using ACES ODT Tonecurve view transform due to it's not an OCIO transformation. Probably it'll be possible to get rid of this tone curve soon (if it'll be proved useless or it'll be implemented as a part of OCIO LUT). - Movie Cache now supports deleter functions for user keys, so such keys could have some allocated data which would be removed as soon as element in cache is being removed. - Movie Cache now support callbacks to check whether current cache element could be removed from a cache due to it wouldn't be accessed anymore. - Re-written cache stuff for display buffers of ImBuf. Now it's using Movie Cache which is global for all ImBufs. Probably it's not implemented in fastest way, would be investigated further and probably changed it performance wouldn't be good enough. |
Revision d008807 by Campbell Barton June 27, 2012, 17:48 (GMT) |
style cleanup: header comments, use more doxy compat formatting |
Revision ae2f3a4 by Antonis Ryakiotakis June 27, 2012, 17:08 (GMT) |
Fix for #31581, UVs shrink on edge slide. Issue is that all loops of a face adjacent to the sliding verts were getting project-corrected. Introduced a test to only project the affected loops. The projection code introduces a small offset to the boundaries so that any boundary tests can work as expected, but this leads to shrinking of the barycentric coordinates of the projection, causing a shrink of the uvs in turn. This even affects the uvs that -should- be affected though the unfixed behavior works strangely in a correctish way (my guess is because the projection uses the same face as the opposite sliding loop). I fixed the behaviour by taking the mean value of the uvs. This won't support seams but current code doesn't either. Also, all CustomData to exhibit this unfixed behaviour. I only fixed the uv case, other data (Vcolors, etc) will have discontinuities when edge sliding. I expect that the CorrectUV code I am working on may address some of these issues. Also, added NULL checks for utility function (was intended for this bug but wasn't needed after all) |
Revision df20154 by Antonis Ryakiotakis June 27, 2012, 15:39 (GMT) |
Utility function to get the first loop of a vert. Behaves identical to the iterator initialization function. |
Revision bb1432f by Campbell Barton June 27, 2012, 14:36 (GMT) |
svn merge ^/trunk/blender -r48321:48333 |
Revision 7518654 by Campbell Barton June 27, 2012, 14:01 (GMT) |
add access to dissolve_limit from python. |
Revision 78ae6ac by Campbell Barton June 27, 2012, 09:51 (GMT) |
utility function to get the points inside a list of planes. |
Revision 9beef74 by Campbell Barton June 27, 2012, 05:59 (GMT) |
style cleanup: also some spelling correction. |
Revision 3e305c1 by Campbell Barton June 26, 2012, 21:40 (GMT) |
bmesh.ops module for bmesh operator access, only remove_doubles and convex_hull at the moment. |
Revision 4b4eace by Campbell Barton June 26, 2012, 20:36 (GMT) |
svn merge ^/trunk/blender -r48313:48321 |
Revision 200584e by Campbell Barton June 26, 2012, 16:58 (GMT) |
fix for a handful of memory leaks relating to parsing and allocating arbitrary sized vectors from python args. Vector.dot() was always leaking memory, and would crash if args sizes didnt match. These errors were introduced with n-dimensional vector support. also fixed an error with bmesh py api allocation. |
Revision c837fcb by Sergey Sharybin June 26, 2012, 15:29 (GMT) |
Revision de00723 by Sergey Sharybin June 26, 2012, 15:26 (GMT) |
Fix for crash of keying screen node in cases when there's no triangulation generated for tracks setup |
Revision e32c467 by Campbell Barton June 26, 2012, 14:49 (GMT) |
mathutils.Vector(kw=value) wasn't raising an error as it should. |
|
|
|


Master Commits
MiikaHweb | 2003-2021