public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "mark at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug AWT/17952] New: Windows don't show with window manager that supports _NET_REQUEST_FRAME_EXTENTS Date: Tue, 12 Oct 2004 18:14:00 -0000 [thread overview] Message-ID: <20041012181409.17952.mark@gcc.gnu.org> (raw) With window managers that support _NET_REQUEST_FRAME_EXTENTS no AWT (or Swing) windows ever show. There is only the following error message. (:6725): Gdk-WARNING **: /home/mark/sources/gtk+/gdk/x11/gdkdrawable-x11.c:912 drawable is not a pixmap or window This was caused by the patch that delayed window realization. The window sizing logic should be moved into the "realize" signal's callback chain so that we are sure that window->window is non-NULL when I make the request to the window manager. See also this email thread: http://gcc.gnu.org/ml/java-patches/2004-q4/msg00090.html -- Summary: Windows don't show with window manager that supports _NET_REQUEST_FRAME_EXTENTS Product: gcc Version: 4.0.0 Status: UNCONFIRMED Severity: critical Priority: P2 Component: AWT AssignedTo: fitzsim at redhat dot com ReportedBy: mark at gcc dot gnu dot org CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=17952
next reply other threads:[~2004-10-12 18:14 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-12 18:14 mark at gcc dot gnu dot org [this message] 2004-10-12 18:14 ` [Bug AWT/17952] " mark at gcc dot gnu dot org 2004-10-12 19:07 ` cvs-commit at gcc dot gnu dot org 2004-12-01 0:31 ` cvs-commit at gcc dot gnu dot org 2005-02-09 4:11 ` fitzsim at redhat dot com 2005-02-21 8:13 ` fitzsim at redhat dot com 2005-02-22 4:12 ` pinskia at gcc dot gnu dot org 2005-02-22 4:50 ` fitzsim at redhat dot com 2005-02-22 6:26 ` cvs-commit at gcc dot gnu dot org 2005-02-22 6:27 ` fitzsim at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20041012181409.17952.mark@gcc.gnu.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).