Hi Nathan,
it finally works. What helped was your pointer into the ewl_embed_test.c
- there you have ewl_object_fill_policy_set(EWL_OBJECT(emb),
EWL_FLAG_FILL_ALL) - which seems to be necessary to get move and
resizing the embedded ewl working. Without doing that, it exposes the
clipping problem
I committed a change to ewl_embed_test that shows an EWL embed being
used inside of a swallowed edje part. This seems to be working quite
well, so please take a look at how the third ewl_embed is setup in
src/bin/ewl_embed_test.c. If you are still having issues, feel free to
send some code
Hi Michael,
You can now use the Etk_Embed widget to have Etk's widgets in your evas
programs, but Etk is still dependant on X. It means that you can now
use Etk widgets in a framebuffer program, but since Etk is still linked
to X, you'll need to have X installed, even if it is not used :o
Next
Are you moving the evas object returned from the ewl embed? I'll try
to write up a similar test case and add it to ewl_embed for an example
(and debugging if there's an issue).
Thanks,
Nathan
On 6/22/06, Michael 'Mickey' Lauer
[EMAIL PROTECTED] wrote:
Am Dienstag, den 20.06.2006, 23:26 -0500
I was either not aware of, or forgot about these issues. Peter fixed
the (0, 0) issue, and I committed a fix for embedding multiple widget
areas. Both of these fixes are in CVS now, so update and if you run
into similar problems again, please let us know.
Thanks,
Nathan
On 6/18/06, Michael
Hi,
ecore_x looks like an optional dependency for ETK. Would it be possible
to run it without X at all? I already work with framebuffer-only
versions of evas, ecore and edje. It would be nice to have access to a
full blown widget toolkit without needing X. While I can do a lot of
impressive
Hi Michael,
The ./configure script indeed looks for Ecore_X and doesn't complain if
Ecore_X is not detected but there are still some pieces of code in Etk
that uses Ecore_X without the #ifdef/#endif thing (Etk_Popup_Window
for example), so for now, you can't compile Etk for the framebuffer.
But
If you want a widget set that already supports the framebuffer, you
could use EWL. If you want ETK specifically, you have to use X until
it supports other engines or nesting in an existing Evas.
On 6/18/06, Michael 'Mickey' Lauer
[EMAIL PROTECTED] wrote:
Hi,
ecore_x looks like an optional
Simon wrote:
But we plan to put all the Ecore_X-dependant code in a separated dir
(ie the files etk_dnd.c, etk_selection.c, etk_clipboard.c,
etk_popup_window.c, ...) so a framebuffer port could be really easily
written.
That's good news. I'll keep holding my breath for that :)
Nathan wrote:
