> oooh! you should read your code more carefully! :)
> the gdb backtrace says u die in evas_engine_info_set() - which makes sense. u
> didnt notice this because your printf("test"); has no \n - thus no newline and
> it doesnt get flushed and u dont see it. so the reason it dies is you are not
> setting up the engine info data at all (no display pointer, etc. etc.) so evas
> of course has a very bad day if u dont tell it what to do with the target
> rendering surface properly... :) the wrappers set this all up for you 
> correctly
> and save effort - but if you want to DIY - make sure u set up the engine info
> properly. :)

Um, yea, you are right ^^", but Ithink I vill not go for the pain, I
tried it with the wrapper and it works really fine. Sorry for stealing
your time.

cya
Christoph
-- 
Christoph Peltz <[EMAIL PROTECTED]>

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

Reply via email to