Revision f09f89d by Maxime Curioni July 31, 2008, 11:20 (GMT) |
soc-2008-mxcurioni: added a Freestyle panel to select a style at run-time, by specifying its pathname. By default, it is loaded with the contour.py path. |
Revision 3010f2b by Maxime Curioni July 31, 2008, 08:50 (GMT) |
soc-2008-mxcurioni: the native Python system now supports cross-language polymorphism for the following classes: BinaryPredicate0D (__call__), BinaryPredicate1D (__call__), UnaryPredicate0D (__call__), UnaryPredicate1D (__call__), StrokeShader (shade), ChainingIterator (init, traverse). Other methods could easily be supported in the future. The method now works as planned for the contour style. For style modules with Python shaders, there still is a problem that I will fix right away. |
Revision 1b78333 by Ken Hughes July 30, 2008, 21:52 (GMT) |
Tools ----- Minor changes to boolean code; add an new include file to gather various #defines global to the boolean system. Currently, this just allows control of whether some debugging code is compiled or not. This is a precursor commit for some other boolean optimizations/cleanups. But in case that commit is later reverted, this code should still remain. |
Revision 01b1bd4 by Nathan Letwory July 30, 2008, 20:45 (GMT) |
* another commit adding std:: to the sort call (older msvc [<9] choked?) |
Revision 409d0ea by Martin Poirier July 30, 2008, 18:10 (GMT) |
Merge subgraph with closest node, not just first node under threshold. |
Revision 8a8a12e by Benoit Bolsee July 30, 2008, 17:41 (GMT) |
BGE patch: logic optimization part 2: remove inactive sensors from logic manager. With this patch, only sensors that are connected to active states are actually registered in the logic manager. Inactive sensors won't take any CPU, especially the Radar and Near sensors that use a physical object for the detection: these objects are removed from the physics engine. To take advantage of this optimization patch, you need to define very light idle state when the objects are inactive: make them transparent, suspend the physics, keep few sensors active (e,g a message sensor to wake up), etc. |
Revision d053636 by Benoit Bolsee July 30, 2008, 17:22 (GMT) |
Update MSVC project since recent commit |
Revision 7f170c1 by Brecht Van Lommel July 30, 2008, 16:15 (GMT) |
Bugfixes: fix for two memory leaks related to dupligroups, and a missing reference count in the trackto actuator. This showed up as leaked pose data, but actually the whole object was not being freed. |
Revision 9667af9 by Ian Thompson July 30, 2008, 11:27 (GMT) |
Oops, forgot about horizontal/vertical scrolling. Cursor, selections and brackets should now draw correctly when scrolled. |
Revision 2d3a57e by Daniel Genrich July 30, 2008, 11:21 (GMT) |
Bugfix for mesh deformer under windows --> uninitialized variable was used in meshdeform_inside_cage() |
Revision f3a4f3a by Joshua Leung July 30, 2008, 09:20 (GMT) |
Grease Pencil Bugfixes: * Segfaults with eraser should now be fixed * Attempted fixed for sequencer redraw problems with buttons |
Revision 7b819bc by Joshua Leung July 30, 2008, 09:07 (GMT) |
== Grease Pencil - Eraser (First Draft) == This commit introduces the ability to erase strokes. Admittedly, the code for this is not totally stable yet, and doesn't always produce optimum results. I'm committing now for backup purposes. It currently uses the lasso code to check whether segments of the strokes (a segment occurs between two recorded points) occur inside a region defined by the 'eraser' stroke, or any intersections it makes with the 'eraser' stroke. There are multiple ways to erase strokes: * With 'Draw Mode' on, use RMB-drag to erase * With a tablet, use the 'eraser' end of the stylus * Hold the Alt Key, and use the 'selection' mouse-button (i.e. LMB if mouse-button swapping is on, RMB otherwise) to erase. For this one, this is necessary to avoid overriding the view-rotation hotkey combo for 2-button mice! Todo: * 3d-strokes are not correctly mapped back to screen-space for sampling yet * Drawing of eraser strokes is still not distinctive enough * After running a few times, may cause stack corruption/segfaults, so be careful! == Bugfixes == * Grease-Pencil Onion-Skinning works again. Onionskining was being supplied the wrong frames, and the alpha factor was still the old one used for 0-255 ranged colour values |
Revision a482f64 by Maxime Curioni July 30, 2008, 01:51 (GMT) |
soc-2008-mxcurioni: Tested SWIG-less environment more and understood why the former predicate methods were not working. As Stéphane had mentioned a few months ago, Freestyle uses SWIG directors to provide cross-language polymorphism. The API and the system I had provided did not support that feature and only implementations in C++ were supported. To correct the problem, after researching how directors are implemented in SWIG, I provided the same functionality. So far, I only provided the code for the UnaryPredicate1D class and it works. The implementation is in intern/python/Director.cpp and Operators.cpp. I will port the remaining directors tonight and continue to test it. To prevent strokes from piling up after each render, I clear the canvas at each render now (as it should have been all along) |
Revision 140a8b7 by Ian Thompson July 30, 2008, 00:05 (GMT) |
Bracket matching now works with word-wrap. Mouse selection and scrolling to do. |
Revision 34bb446 by Mal Duffin July 29, 2008, 22:44 (GMT) |
Simple changes to Motion Actuator UI. This includes... - Renaming dLoc and dRot as Loc and Rot ( as well as changing the tooltip to location and rotation ). dLoc and dRot are programming terms, not user terms. - Placing Loc and Rot as the two initial shown values, so that the physical ones are all shown together. I also changed it so that only Loc and Rot are shown in the UI, unless the object is Dynamic ( as the other values only make sense if it is dynamic ). These are just a few simple changes, that should make a lot of difference to users when learning how to use the GE. -------------------------------------- Things I'd *really* like to do to this, when I get a chance to code Blender again ( hopefully in a few days time, after I have finished teaching on the GE course )... Color / Colour tint the X,Y and Z entry boxes as slightly red, green and blue, to reflect the colour of the axis / transform gizmo ...or... Just show X,Y and Z labels above all of the values. Getting to grips with the whole XYZ thing is very confusing for users, esp when they are presented with 6 x 3 entry boxes. |
Revision e04c48d by Nathan Letwory July 29, 2008, 21:56 (GMT) |
* making sure BGE compiles after brecht's big commit (r15867). Needed <algorithm> to compile with msvc. |
Revision 7f3c279 by Mal Duffin July 29, 2008, 21:49 (GMT) |
Copy Attributes now has option to copy all physical attributes. There existed two options to copy only the mass, and only the damping, but no option to copy all of the physical attributes. This patch adds in this option, right under the Mass and Damping listings. |
Revision ca951b3 by Mal Duffin July 29, 2008, 20:28 (GMT) |
Am teaching a GE course this week, and am finding some small issues that I'm hoping to patch. This one deals with the very small default clipend value ( 100.0 ) when pressing P to run the GE from a non-camera view. ( ie if the user zooms out a bit from the default box area, the box will get clipped out of view, so it's a WFT from the user ) To see what this fixes, load up Blender default scene, go into perspective, and press P. Everything looks grand. Now, zoom out until the box is about 10 pixels high, and press P again. The box will disappear / be clipped out. I've set the clip end to the maximum ( 5000 ) as defined in Camera.h. This should be suitable for inclusion in 2.47 branch also. |
Revision 2efd741 by Martin Poirier July 29, 2008, 20:20 (GMT) |
Bug fixes: Retag subgraphs when merging, to prevent loops Mark missing up link in multi resolution as NULL Ignore hidden vertices when propagating weight between islands |
Revision 039814f by Daniel Genrich July 29, 2008, 18:07 (GMT) |
No long needed here (win64 cleanup) |
|