[Opal-commits] opal changelog.txt,1.10,1.11 todo.txt,1.52,1.53
Status: Inactive
Brought to you by:
tylerstreeter
|
From: tylerstreeter <tyl...@us...> - 2005-03-12 01:21:52
|
Update of /cvsroot/opal/opal In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv17179 Modified Files: changelog.txt todo.txt Log Message: added VolumeSensor Index: changelog.txt =================================================================== RCS file: /cvsroot/opal/opal/changelog.txt,v retrieving revision 1.10 retrieving revision 1.11 diff -C2 -d -r1.10 -r1.11 *** changelog.txt 26 Feb 2005 10:22:22 -0000 1.10 --- changelog.txt 12 Mar 2005 01:21:07 -0000 1.11 *************** *** 2,8 **** , 2005 ------------------------------------------ ! * Overhauled XML loading system ! * New additional object creation system: all objects can be created from/saved to a data structure ! * Separate Joint types were combined into a single Joint class * Numerous API changes * Various bug fixes --- 2,11 ---- , 2005 ------------------------------------------ ! * New additional object creation system: all objects can be created from/saved to a data object ! * EventHandler was changed to a base class for CollisionEventHandler and JointBreakEventHandler ! * Collision events now get queued up during collision detection and handled at the end of each time step ! * Added RaycastSensor, VolumeSensor ! * Overhauled XML loading system; now all Solid, Shape, Joint, Motor, and Sensor data can be loaded from OPAL XML files ! * Joints have a parameter to allow contacts between connected Solids or not * Numerous API changes * Various bug fixes Index: todo.txt =================================================================== RCS file: /cvsroot/opal/opal/todo.txt,v retrieving revision 1.52 retrieving revision 1.53 diff -C2 -d -r1.52 -r1.53 *** todo.txt 9 Mar 2005 02:09:51 -0000 1.52 --- todo.txt 12 Mar 2005 01:21:07 -0000 1.53 *************** *** 2,5 **** --- 2,8 ---- ================= + * additional sensors + - vel, accel, incline/orientation; relate these to vestibular senses? + * sensors - parse from xml *************** *** 8,14 **** - add to Blueprint finalize function - * fix memory allocation across dll boundary - - volume collision check results -> put results in a specific class - * make trimeshes work --- 11,14 ---- *************** *** 41,60 **** - contact filtering? - * event handling/callbacks - - collisions - - broken joints - - beginning of step - * look at (and maybe remove) mass ratio stuff - there may be a problem when you have a tiny object between two massive objects; one massive object should affect the other but can't - removing this also may fix the problem where a huge object dropped on a tiny object traps the smaller one underneath; the small one constantly wriggles around, but the large one doesn't move. ! * should all modes with multiple options (e.g. spring motor, accel sensor) take bit flags? * separate Joint back into separate subclasses? ! * separate Motors with different modes into separate types? ! ! * use custom motors? - for one thing, we can't use them in xml - if we use them, should we also have custom sensors? --- 41,54 ---- - contact filtering? * look at (and maybe remove) mass ratio stuff - there may be a problem when you have a tiny object between two massive objects; one massive object should affect the other but can't - removing this also may fix the problem where a huge object dropped on a tiny object traps the smaller one underneath; the small one constantly wriggles around, but the large one doesn't move. ! * should all objects with multiple modes of operation (e.g. spring motor, accel sensor) take bit flags? ! - or just separate objects with different modes into separate types? * separate Joint back into separate subclasses? ! * get rid of custom motors? - for one thing, we can't use them in xml - if we use them, should we also have custom sensors? *************** *** 71,77 **** ============== - * joint flags - - allow collisions between joined solids - * GearedMotor - talk to Jim Bernard --- 65,68 ---- |