After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 1492 - Signal on realization failure for GtkPlug
Signal on realization failure for GtkPlug
Status: RESOLVED DUPLICATE of bug 50919
Product: gtk+
Classification: Platform
Component: Widget: Other
1.3.x
Other other
: Normal enhancement
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 1999-06-15 17:55 UTC by Jonathan Blandford
Modified: 2011-02-04 16:09 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Jonathan Blandford 2001-01-27 19:46:26 UTC 
Package: gtk+
Version: 1.2
Severity: Wishlist

I'd like a signal in gtk-socket to know if the widget was unable to
realize in the assigned socket.

Thanks,
-Jonathan




------- Additional Comments From otaylor@redhat.com 1999-06-16 14:04:03 ----

Subject: Re: Bug#1492:
From: Owen Taylor <otaylor@redhat.com>
To: 1492@bugs.gnome.org
Message-Id: <ybeu2s8aup8.fsf@fresnel.labs.redhat.com>
Date: 16 Jun 1999 14:04:03 -0400


The idea here, is that when a GtkPlug gets realized,
if its parent widget has been destroyed in the meantime,
GTK+ creates the plug as a toplevel window because
it has no idea what to do. It might be nice to
be able to customize this behavior, and, for instance,
do a exit() instead.




------- Bug moved to this database by debbugs-export@bugzilla.gnome.org 2001-01-27 14:46 -------
This bug was previously known as bug 1492 at http://bugs.gnome.org/
http://bugs.gnome.org/show_bug.cgi?id=1492
Originally filed under the gtk+ product and general component.

Reassigning to the default owner of the component, gtk-bugs@gtk.org.
Comment 1 Havoc Pennington 2001-01-28 05:16:17 UTC 
Another one for the 2.0 TODO list
Comment 2 Havoc Pennington 2001-01-29 19:39:39 UTC 
Put all GTK 1.3.x bugs on 2.0.0 milestone
Comment 3 Havoc Pennington 2001-01-29 19:49:57 UTC 
Setting API-affecting bugs to the API freeze milestone
Comment 4 Owen Taylor 2001-03-29 21:31:15 UTC 
In the XEMBED protocol, the plug is passed to the socket
which is responsible for mapping it, so this can't happen.


*** This bug has been marked as a duplicate of 50919 ***