Re: Client Side windows in GDK (GTK+-2.18.xxx)
Hi Tor Lillqvist, Thanks for valuable information. I was wrong. I was thinking that DirectFB stuff in gtk+ is also maintained. I am working on understanding client side windows and debugging the code. Thanks & Regards AshokKumar.G On Thu, Mar 11, 2010 at 12:39 AM, Tor Lillqvist wrote: > > Could some one help me on this how to proceed further? > > Read the code, understand how it works, debug, fix problems, submit > patches in bugzilla? > > Please understand that the directdb stuff in gtk+ is very close to > unmaintained, as far as I know. > > --tml > ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Client Side windows in GDK (GTK+-2.18.xxx)
Hi,
I am using webkitgtk+ port on DirectFB. When I upgraded to
gtk+2.18.3, 2.18.7 versions on DirectFB-1.2.9, gtk+ test application is
getting aborted. While gtk_init() is called _gdk_window_new is getting
called (root window and creating dfb implementation window), and in the same
function (gdk_window_new) application is getting aborted at
else if (native)
{
event_mask = get_native_event_mask (private);
/* Create the impl */
_gdk_window_impl_new (window, real_parent, screen, visual,
event_mask, attributes, attributes_mask);
private->impl_window = private;
/* This will put the native window topmost in the native parent,
which may
* be wrong wrt other native windows in the non-native hierarchy, so
restack */
if (!_gdk_window_has_impl (real_parent)){
sync_native_window_stack_position (window); ---> *control goes
into this function* which will call below specified functions.
}
}
static GdkWindowObject *
find_native_sibling_above (GdkWindowObject *parent,
GdkWindowObject *child)
and this will call below function
static GdkWindowObject *
find_native_sibling_above_helper (GdkWindowObject *parent,
GdkWindowObject *child)
It is failing aborting with the following message
Caught signal 11 (at 0x28, invalid address) <--
(!!!) *** WARNING [still objects in 'Window Pool'] *** [object.c:241 in
fusion_object_pool_destroy()]
(!!!) *** WARNING [still objects in 'Layer Region Pool'] *** [object.c:241
in fusion_object_pool_destroy()]
(!!!) *** WARNING [still objects in 'Layer Context Pool'] ***
[object.c:241 in fusion_object_pool_destroy()]
(!!!) *** WARNING [still objects in 'Surface Pool'] *** [object.c:241 in
fusion_object_pool_destroy()]
In this case there is no SIGSEGV signal sent to test application. Only
SIGABRT was sent to test application.
But with the older gtk version i.e. 2.16.1 every thing works fine. But since
webkit changes gtk+ should also be updated to newer version.
Could some one help me on this how to proceed further?
Thanks & Regards
AshokKumar.G
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
gtk+-2.18.7 application on DirectFB Back End is aborting
Hi, Today I tried gtk+-2.18.7 release on DirectFB backend. Build was successful. But when I tried to run test applications it crashed. But the earlier I used the version gtk+-2.16, it is working fine, but have some dependencies with Webkit, so I have to update my gtk+ version. I added the prints in to debug it but I don't have clues. please find the attached two files. 1. gtk_abort_log.txt 2. testapp.c Could some one help me on this? Thanks & Regards AshokKumar.G It's never too late to fail. GTHREAD IS NOT SUPPORTED gtkmain.c IA__gtk_init_check 960 after gtk_parse_args now returning gdk_display_open_default_libgtk_only gdk.c IA__gdk_display_open_default_libgtk_only 318 Entry gdk.c IA__gdk_display_open_default_libgtk_only 321 gdk_initialized is not true gdk.c IA__gdk_display_open_default_libgtk_only 326 default display is not there so open it now gdkdisplay-directfb.c IA__gdk_display_open 72 Entry with display_name (null) commandline read: youtubeXL gdkdisplay-directfb.c IA__gdk_display_open 86 after DirectFBInit success ~~| DirectFB 1.2.9 |~~ (c) 2001-2008 The world wide DirectFB Open Source Community (c) 2000-2004 Convergence (integrated media) GmbH (*) DirectFB/Core: Multi Application Core. (2010-02-17 18:48) (*) Fusion/SHM: Using MADV_REMOVE (2.6.27.39 >= 2.6.19.2) (*) Direct/Thread: Started 'Fusion Dispatch' (-1) [MESSAGING OTHER/OTHER 0/0] <8388608>... (*) DirectFB/TESTGFX: use GFX plane (*) Direct/Thread: Started 'Linux Input' (1706) [INPUT OTHER/OTHER 0/0] <8388608>... (*) DirectFB/Input: Inafra-Red (1) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (1707) [INPUT OTHER/OTHER 0/0] <8388608>... (*) DirectFB/Input: Microsoft Microsoft 5-Button Mo (2) 0.1 (directfb.org) (*) Direct/Thread: Started 'Linux Input' (1708) [INPUT OTHER/OTHER 0/0] <8388608>... (*) DirectFB/Input: Dell Dell USB Keyboard (3) 0.1 (directfb.org) (*) DirectFB/Graphics: Test Driver gdkdisplay-directfb.c IA__gdk_display_open 93 after DirectFBCreate success gdkdisplay-directfb.c IA__gdk_display_open 98 before directfb->GetDisplayLayer gdkdisplay-directfb.c IA__gdk_display_open 100 directfb is not NULL gdkdisplay-directfb.c IA__gdk_display_open 105 after directfb->GetDisplayLayer gdkdisplay-directfb.c IA__gdk_display_open 114 before directfb->GetInputDevice gdkdisplay-directfb.c IA__gdk_display_open 123 after directfb->GetInputDevice gdkdisplay-directfb.c IA__gdk_display_open 127 before _gdk_directfb_keyboard_init gdkdisplay-directfb.c IA__gdk_display_open 129 after _gdk_directfb_keyboard_init gdkdisplay-directfb.c IA__gdk_display_open 133 before _gdk_visual_init gdkdisplay-directfb.c IA__gdk_display_open 135 after _gdk_visual_init gdkdisplay-directfb.c IA__gdk_display_open 136 before _gdk_windowing_window_init gdkdraw.c IA__gdk_drawable_get_colormap 274 Entry gdkdraw.c IA__gdk_drawable_get_colormap 276 drawable is null so crash gdkdraw.c IA__gdk_drawable_get_colormap 283 drawable is not drawable so crash gdkdraw.c IA__gdk_drawable_get_colormap 285 before g_return_val_if_fail() (testapp:1701): Gdk-CRITICAL **: gdk_drawable_get_colormap: assertion `GDK_IS_DRAWABLE (drawable)' failed gdkdisplay-directfb.c IA__gdk_display_open 138 after _gdk_windowing_window_init gdkdisplay-directfb.c IA__gdk_display_open 141 _gdk_screen is not NULL gdkdisplay-directfb.c IA__gdk_display_open 145 before call to gdk_screen_set_default_colormap and calling gdk_screen_get_system_colormap gdkdisplay-directfb.c IA__gdk_display_open 148 after call to gdk_screen_set_default_colormap and calling gdk_screen_get_system_colormap (*) Direct/Thread: Started 'EventBufferFeed' (1709) [MESSAGING OTHER/OTHER 0/0] <8388608>... gdk.c IA__gdk_display_open_default_libgtk_only 329 after gdk_display_open gdk.c IA__gdk_display_open_default_libgtk_only 340 display is not null now call gdk_display_manager_set_default_display gdk.c IA__gdk_display_open_default_libgtk_only 345 return display gtkwindow.c gtk_window_realize 4682 Entry gtkwindow.c gtk_window_realize 4715 after GTK_WIDGET_SET_FLAGS(widget, GTK_REALIZED) gtkwindow.c gtk_window_realize 4721 GDK_WINDOW_TOPLEVEL gtkwindow.c gtk_window_realize 4784 window doesn't have any frame gdkdraw.c IA__gdk_drawable_get_colormap 274 Entry gdkdraw.c IA__gdk_drawable_get_colormap 278 drawable is not null so proceed further gdkdraw.c IA__gdk_drawable_get_colormap 281 drawable is drawable so proceed further gdkdraw.c IA__gdk_drawable_get_colormap 285 before g_return_val_if_fail() gdkdraw.c IA__gdk_drawable_get_colormap 287 after g_return_val_if_fail() gdkwindow.c gdk_window_real_get_colormap 4794 Entry gdkwindow.c gdk_window_real_get_colormap 4796 drawable is not null and address 0x3a800 gdkwindow.c gdk_window_real_get_colormap 4801 drawable is GDK WINDOW gdkwindow.c gdk_window_real
Re: Regarding GTK Entry keys
Hi Sanny, Thanks for your reply. I am doing it. Regards & Cheers AshokKumar.G +919986132890 On Fri, Feb 12, 2010 at 1:26 PM, Sanny Chawla wrote: > Hi Ashok, > > This might be because of the incorrect hardware keycode for the function > keys on your embedded system. The key events that you mentioned (Backspace , > Delete , etc) are activated through key bindings in Gtk which needs a valid > hardware keycode. > > You can try modifying the keymap table for this. xmodmap utility can be > helpful for the same. > > Cheers , > Sanny > > > On Wed, Feb 10, 2010 at 4:27 AM, AshokKumar G < > ashok.sysprogram...@gmail.com> wrote: > >> Hi, >> I am new to GTK+ programming. I have created a test application >> with GtkEntry on embedded system based on ARM and backend target is >> DirectFB-1.2.9. I am able to enter the text into GtkEntry field. But when >> I >> use BackSpace, Delete, Arrow Keys (left or right for navigation), no >> action >> is taken. In my test application I have registered call back >> key-press-event >> to verify whether event is coming or not, when I press backspace the event >> is coming and I am returning FALSE from that call back function. But no >> character is getting deleted on backspace/delete key press. >> But when I run my same test application on PC GTK+same version >> with >> backend target X11, then all the actions are performing as expected. >> Could some one help me on this? >> >> Thanks & Regards, >> AshokKumar.G >> >> ___ >> gtk-app-devel-list mailing list >> gtk-app-devel-list@gnome.org >> http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list >> > > ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
Regarding GTK Entry keys
Hi, I am new to GTK+ programming. I have created a test application with GtkEntry on embedded system based on ARM and backend target is DirectFB-1.2.9. I am able to enter the text into GtkEntry field. But when I use BackSpace, Delete, Arrow Keys (left or right for navigation), no action is taken. In my test application I have registered call back key-press-event to verify whether event is coming or not, when I press backspace the event is coming and I am returning FALSE from that call back function. But no character is getting deleted on backspace/delete key press. But when I run my same test application on PC GTK+same version with backend target X11, then all the actions are performing as expected. Could some one help me on this? Thanks & Regards, AshokKumar.G ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
