Hello.
On Tue, 2008-04-29 at 16:44, Stefan Schmidt wrote:
On Sat, 2008-04-12 at 16:46, Michael Stapelberg wrote:
There may still be bugs, so I'd appreciate some testing. Please don't
comment
the #define DEBUG out and let e17 log to a file, for example using startx
Build log for Enlightenment DR 0.17 on 2008-04-30 07:09:03 -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
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 I can't compile
the
On Wed, Apr 30, 2008 at 11:40 AM, andres [EMAIL PROTECTED] wrote:
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
Just as a change of pace from the evas filters/transforms stuff...
here's a simple ability that could be useful in evas right now.
There are many, many kinds of custom evas object types one could
define... and some of these might involve using external libs (either
in their
For the last couple of days I've been getting some pretty bad segfaults.
I can reproduce it every time, by doing certain things to one of the
shelves (adding modules, moving it to a different layer). When
debugging, most of the time, the stack trace passes through the
winselector module. Upon
As we discussed at IRC, probably this policies can be handled on top
of currently existing Size_Hints and no other members should be added
to the struct.
Also agreed at IRC is that most difficult part is to get all the
requirements written, we should start with V/HBox as they're useful
and
On Wed, Apr 30, 2008 at 7:59 PM, Jose Gonzalez [EMAIL PROTECTED] wrote:
As we discussed at IRC, probably this policies can be handled on top
of currently existing Size_Hints and no other members should be added
to the struct.
Also agreed at IRC is that most difficult part is to
I wrote:
There's a very simple way to have this ability in evas right,
one that requires very few internal additions and no modifications
to any of the current stuff.
That should've read ...to have this ability in evas right now,
Note that this deosn't mean that
Gustavo wrote:
One of the things I see going on with this kind of thing is
an attempt to put more and more 'widgetry/layout' kinds of needs
into evas objects in a generic way. The 'problem' with some of this
is that evas objects don't have any real notion of 'inheritance' or
10 matches
Mail list logo
