andres schrieb:
Hello, in order to implement the layout objects for my SoC project I need to
know if it would be possible to add size hints to Evas Objects.
I attached a patch file with the required changes. I tried following the
implementation of size hints since its a similar concept but
Gustavo Sverzut Barbieri schrieb:
Just to make clear: what goes into Evas_Object is the hints. They
could be represented as allocated structs managed with
evas_object_data_*(), but since they're so common we could 1) make it
more standard, helping integration and
I don't see where they are so
Build log for Enlightenment DR 0.17 on 2008-05-02 07:08:56 -0700
Build logs are available at http://download.enlightenment.org/tests/logs
Packages that failed to build:
enna http://download.enlightenment.org/tests/logs/enna.log
epdf http://download.enlightenment.org/tests/logs/epdf.log
evolve
On Fri, May 2, 2008 at 11:23 AM, Peter Wehrfritz [EMAIL PROTECTED] wrote:
Gustavo Sverzut Barbieri schrieb:
Just to make clear: what goes into Evas_Object is the hints. They
could be represented as allocated structs managed with
evas_object_data_*(), but since they're so common we could
Gustavo Sverzut Barbieri schrieb:
On Fri, May 2, 2008 at 11:23 AM, Peter Wehrfritz [EMAIL PROTECTED] wrote:
You can use a hash or a tree instead.
sure, but then you waste almost a kb on the bucket allocation. it's a
trade off, no free lunch.
(btw, yes, evas speed up this by
Gustavo wrote:
One other aspect that needs to be addressed has to do with the
very notion Gustavo mentioned about negotiating buffer sizes that
a filter/transform might need for putting results to.. and in fact
this also covers things like calculating update rects when dealing
