Also removed edbus_object_interfaces_added_callback_add/del() because we already
have object events for that.
Patch by: José Roberto de Souza <zehortigoza@profusion.mobi>
SVN revision: 80680
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
José Roberto de Souza
Bruno Dilly
Stefan Schmidt
Cedric BAIL
Leandro Dorileo
Bluezery
Carsten Haitzler
Daniel Juyung Seo
Rui Seabra
Massimo Maiurana
Sebastian Dransfeld