Hello,
my application has a problem at exit time. I get this message printed
multible times at exit:
*** ECORE ERROR: Ecore Magic Check Failed!!!
*** IN FUNCTION: ecore_event_filter_del()
Input handle has already been freed!
*** NAUGHTY PROGRAMMER!!!
*** SPANK SPANK SPANK!!!
*** Now go fix
Hello,
I've a ugly problem with refreshing in my Evas/Edje application. I have
multible Evas objects which take the same place and are only shown or
hidden in some situations.
There're two screens (one with a map and one with a black border). I do
this:
...
...(user screen change)...
Patch does the following:
- 'options' menu entry moved from 'file' to 'edit' menu
- 'set as wallpaper' menu entry moved from 'edit' to file' menu
- new menu entry 'fullscreen' added to view menu
- new option for showing all filetypes
- new option for showing hidden files and directories
- use %s
On 5/29/07, Brian 'morlenxus' Miculcy [EMAIL PROTECTED] wrote:
Patch does the following:
- 'options' menu entry moved from 'file' to 'edit' menu
- 'set as wallpaper' menu entry moved from 'edit' to file' menu
- new menu entry 'fullscreen' added to view menu
- new option for showing all
On 5/27/07, Gustavo Sverzut Barbieri [EMAIL PROTECTED] wrote:
I'm not sure about overhead, need to evaluate on small/embedded
devices (I'm more than surprised by the bottlenecks I've found while
running on omap2420/arm6/maemo).
As for API, most places uses Evas_Coord, which now is typedef'ed
On Mon, 2007-28-05 at 21:14 -0500, Nathan Ingersoll wrote:
Evas_Coord was originally defined as a float, so you may see a few
remnants like that. Also there was originally support for non
one-to-one mappings of evas coordinate space to world coordinates.
Do you know the reason for the change
On 5/28/07, Jason Tackaberry [EMAIL PROTECTED] wrote:
Do you know the reason for the change to int? Was it just because none
of the engines took advantage of it? Obviously I'd like to see
Evas_Coord be a float. :) But perhaps the reason for the change to int
is indicative of a deeper