Well, I'm out of easy ideas.
The "(*) SaWMan/Watcher: Process 9986 [3] has exited ABNORMALLY!" is not
good.
I suggest enabling the debug log messages of directfb: you can configure
your directfb with --enable-debug and then put "debug" and
"log-file=<yourlogfilename>" in directfbrc to see what is going on.
Greets
Niels
Balaji Rao R wrote:
On Wed, Apr 22, 2009 at 5:47 PM, Niels Roest <ni...@directfb.org> wrote:
Hi.
the "failed to get exclusive access" is normal; it is because of the
force-windowed command-line option: this will cause the app, when it
accesses the primary surface, to fail, causing it to fall back to using a
window instead.
Hi Niels,
Ok, great.
are you sure df_andi is working? you can try to run it stand-alone, like it
is started with testman:
df_andi --dfb:mode=640x480,force-windowed
Yes, it works. I've just verified it now.
What else can I do ?
Thanks,
Balaji
_______________________________________________
directfb-users mailing list
directfb-users@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-users mailing list
directfb-users@directfb.org
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
