I think the colormap one is the most annoying and the device failure is very bad. The list of unimplemented functions should be done first. Most have a Warning and fail resonably but not all. If you don't mind can you give me a list of examples that aborted.
Thanks this email is very helpful. On 7/11/05, swin <[EMAIL PROTECTED]> wrote: > Mike Emmel！ > > >I would need to reimplement them using directfb's multi process > >support its possible. > >And its actually high on my todo list since I use the functions in my code :) > > > >Here is my todo list. > > > >Build with gcc 4.0 fix compile problems. > >Upgrade to gtk 2.7.2 and keep up from the on trying to be less than a > >week behind. > >List functions that need implementation and solicit help. > >Get a formal buglist going. > >Start leak/performance testing. > > I'm doing some leak/performance testing too, use multi process enabled. > this is the test for gimp: It can be launched, but with some warring like > this: > > (gimp:9007): Gdk-CRITICAL **: gdk_drawable_set_colormap: assertion `cmap == > NULL || gdk_drawable_get_depth (drawable) == cmap->visual->depth' failed > > (gimp:9007): Gdk-WARNING **: No colormap in gc_get_background > > (gimp:9007): Gdk-CRITICAL **: gdk_screen_get_monitor_at_point: assertion > `GDK_IS_SCREEN (screen)' failed > > (gimp:9007): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == > gdk_drawable_get_depth (window)' failed > > (gimp:9007): Gtk-CRITICAL **: gtk_paint_box: assertion `style->depth == > gdk_drawable_get_depth (window)' failed > > (gimp:9007): Gimp-Widgets-CRITICAL **: gimp_device_info_get_by_device: > assertion `GDK_IS_DEVICE (device)' failed > > (gimp:9007): Gimp-Widgets-CRITICAL **: gimp_devices_restore: assertion > `GIMP_IS_DEVICE_INFO (device_info)' failed > I think the colormap one is the most annoying and the device failure is very bad. The list of unimplemented functions should be done first. Most have a Warning and fail resonably but not all. If you don't mind can you give me a list of examples that aborted. > but it can work. when I try to open a jpeg file, it aborted, and print: > > (!) [ 9007: 81119.609] --> Caught signal 11 (at 0x18, invalid address) <-- > (!) Direct/Thread: Killing 'Fusion Dispatch' (9008)! > Killed > (script-fu:9010): LibGimpBase-WARNING **: script-fu: wire_read(): error > > I'm not sure about the problem, anyone known? Dunno Gimp is a huge program Its good to test periodically but I don't think the port is up to using it to trace to many failures yet. Can you get one of the examples to fail in the same way ? > > And alse I use the test program in gtk+2.7.0/tests and gtk+2.7.0/examples > some work well, but some abort, e.g. gtk+2.7.0/examples/clist, does it works > well on your pc? I have no idea to resolve them problem and don't know why, > if someone can have a summarize about the problem, It should be nice for > others > to contribute, after all, most are not the original writter of the code, and > for most, we just can correct some small compile error and so on. > > And I strongly recommand to do these: > List functions that need implementation and solicit help. Yep the unimplemented function list is very important even for me :) > Get a formal buglist going. > Start leak/performance testing. > > swin > [EMAIL PROTECTED] > 2005-07-11 > > > _______________________________________________ > directfb-dev mailing list > [email protected] > http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev > > >
_______________________________________________ directfb-dev mailing list [email protected] http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-dev
