Befoe this we always used the installed modules from the system. That is often
fine but there are cases we would need the local. un-installed, modules. The
coverage check is a example. The system modules normally don't had the options
for coverage enabled and thus would not produce anything for the modules.
Default still stays as it was. You would need to set an env var to use the
local modules.
SVN revision: 80670
With the movement_freedom block it's possible to allow
rotation on axis x and y (not default), for example.
Backface cull support is added in this commit too.
SVN revision: 80616
Introduce a generic resize_cb for soft body faces and fix the
"not pre-resized evas object issue" for multi faces implementation as well.
--This line, and those below, will be ignored--
SVN revision: 80615
Add slices as member of obj smart parent - when it's the case -
so we can restack it when the received evas object is member of a
smart object.
Resize the evas object on ephysics_body_evas_object_set to w=1,
h=1 when its initial/original size is 0, this prevents errors on
evas_object_image_source_set().
Reset the soft body transform on resize - put it back to its
prior position - the one before scaling.
On body_move do not consider the moving of anchored rigid body
enough, move the soft body vertices as well.
--This line, and those below, will be ignored--
SVN revision: 80612
It's going as an action / script instead of an attribute
because it wouldn't fit well as a description.
Rotation can be modified by many circustancies, keeping
as state wouldn't make sense.
SVN revision: 80610
Subject: [E-devel] [Patch][edje] Prevent duplicated inherition of
"after"
When inherting group, "after" of "program" section is also inherited.
But duplicated name of "after" can be also inherited.
I think that multiple "after" can be used but duplicated should be
not. because this seems to be useless.
Is there case that duplicated after usage is used?
Duplicated "target" is prevented. I just copy those codes.
SVN revision: 80565
Most of the actions will be applied to a body using 3 components
(x, y, z). Refactor code around it to avoid duplication, since
basically what changes is the ephysics function to be called.
Also, it will make next actions implementations less error prone.
SVN revision: 80388
Using a callback for body and world update events for that.
It will make it possible to set parts to be relative
to parts that have a physics body.
SVN revision: 80277
state changes
To make it possible, a flag was added: ignore_part_position.
Enabled by default, it will let part position be update
only by physics calculatios. If the body is intended to be
moved when state is changed, the flag must to be explicitely
disabled.
It is required otherwise all the states would inherit position
from "default" and reset body's position.
SVN revision: 80276
+ velocity
Handle cloth cases on velocity functions and consider both rigid
and soft body whenever touching velocities + stoping a body.
+ activation
Activate the body when setting angular velocity.
--This line, and those below, will be ignored--
SVN revision: 80248
It is now you can run programs with names generated dinamically. Say that you
have 10 programs indexed somehow. You can now call them using the following snippet:
script {
new program_id[15], i;
for (i = 0; i < 10; i++) {
snprintf(program_id, 15, "my_program_%d", i+1);
run_program(get_program_id(program_id));
}
}
Signed-off-by: Eduardo Lima (Etrunko) <eduardo.lima@intel.com>
SVN revision: 80199
Use a bigger image to soft button tests, add light on/off button,
use of anchor hardness API.
--This line, and those below, will be ignored--
SVN revision: 80108
This patch introduces a separeted API for handling with anchor hardness,
and fixes small problems with pose and soft body impulses.
--This line, and those below, will be ignored--
SVN revision: 80107
If light configuration has been changed or perspective changed or simply
enabled/disabled force inactive bodies to update.
--This line, and those below, will be ignored--
SVN revision: 80105
Delete the constraints a body belongs to on body removal and avoid
bullet to segfault.
--This line, and those below, will be ignored--
SVN revision: 79850
This patch changes how constraints are created and configured, now we
use a bullet generic implementation which let us operate on the 6
degrees of freedom(linear and angular ones).
We have used 6dof for slider constraint but now we assume 2 types of
constraints, single body - simply ephysics_constraint_add(body) - and a linked
one - ephysics_constraint_linked_add(body1, body2) used to constrain 2 bodies
linked together.
Having said that we introduce the following changes:
+ migrate p2p constraint to 6Dof
We want to have a constraint api generic enouth to allow many different
constraint behaviour, 6Dof was picked to do that, so p2p needs a migration.
+ move ephysics_constraint_slider_* functions
Since the whole constraint infra-sctructure is being migrated to 6Dof the
linear and angular limit functions - previously used only by slider constraint -
now looks more generic enough to be used by constraint in general.
+ add constraint anchor API
Instead of telling the anchoring positioning in the constraint creating we have
set it's default value to the the middle os the body and if the user wants to change
it call ephysics_constraint_anchor_set and reset it.
The ephysics_constraint_anchor_set() considers the canvas coordinate instead of using
the body orientation. So now one can tell a constraints anchor is set to 100, 10, 0
in the canvas coordinate system and not (body_center.x - 20, body_center.y - 5, body_center.z - 1).
+ constraint migrate the bt_constraint
Since we're working only with 6Dof constraints it is reasonable to change the constraints
bt_constraint field to btGeneric6DofConstraint.
+ add 3 axes to constraints
Now constraints API knows about x, y and z axes - linear and angular limiting, anchor
setting and the constraint creation functions are fully supported.
+ constraint calls are renamed
The constraint calls were renamed so ephysics_constraint_p2p_add() now is known as
ephysics_constraint_linked_add() and ephysics_constraint_slider_add() became
ephysics_constraint_add() where the first one is meant for constrain 2 bodies and
the second one for single body constraints.
--This line, and those below, will be ignored--
SVN revision: 79848
Avoiding a circular dependency edje -> elementary -> edje.
It was breaking the build system when option --enable-build-examples was given.
SVN revision: 79839
Every touch down event should be converted into mouse in +
mouse button. So we should let every mouse in event go in the
_ecore_evas_wl_common_cb_mouse_in(), instead of preventing it by
"if (!ee->in)". Besides that, the coordinates carried by mouse in
event should be set to Evas_Public_Data::pointer by calling
_ecore_evas_mouse_move_process().
Signed-off-by: Christopher Michael <cp.michael@samsung.com>
SVN revision: 79818