Re: Problem with reparent (Gtk+-2.12)
- From: Murray Cumming <murrayc murrayc com>
- To: andrew solvo ru
- Cc: gtkmm-list <gtkmm-list gnome org>, gtk-list <gtk-list gnome org>
- Subject: Re: Problem with reparent (Gtk+-2.12)
- Date: Mon, 04 Feb 2008 15:48:03 +0100
On Mon, 2008-02-04 at 17:33 +0300, Andrew E. Makeev wrote:
> Good day,
>
> Few days ago we have downloaded latest packages to build Gtk+-2.12 and
> Gtkmm-2.12 under Win32. The purpose was to fix our application when
> running on Vista OS (selected menu items were blank - Gtk+2.8).
>
> Now we have following problem.
>
> When we are trying to reparent container with toolbar inside from one
> window to another, and then reparent back again, application throws GTK-
> Critical about some widget not ANCHORED or VISIBLE, and next we get
> "widget is not realized" inside map/unmap signal handler.
>
> Using GDB I found that widget is GtkImage inside GtkToolbar from first
> GtkToolbutton.
>
> I have an example where you may see GTK-Critical message when hit
> DOCK/UNDOCK button. There is some work around getting accelerators
> activated/deactivated. But our application have to use it.
Can't this test case be made much smaller?
Can you try it in C too?
> First my thought was "They fixed GtkToolbar reparent problem, probably".
> You know, when you reparent container with toolbar then you will find
> toolbar elements inactive until hide() and show() it in some way. But
> this problem is still here.
>
> So, does someone know if this "new" problem with reparent is known
> issue?
>
> Where in bugzilla I could track it and, probably, attach simple example
> to show the problem?
Under gtkmm or GTK+ in bugzilla.gnome.org, depending on which test case
shows it.
--
murrayc murrayc com
www.murrayc.com
www.openismus.com
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]