public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "myersj at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug AWT/16729] New: Component.print() and Component.printAll() does not affect graphics parameter
Date: Mon, 26 Jul 2004 23:20:00 -0000	[thread overview]
Message-ID: <20040726232019.16729.myersj@gmail.com> (raw)

The print and printAll methods on Component are meant to paint the given
component and its children onto the graphics context.  This is very useful for
performing captures of gui images.  The current implementation of print simply
paints the GTK AWT peer without effecting the graphics context.

When resolving this issue, please make sure that the solution will properly
print when the component is not visble on screen (hidden behind other windows or
off the edge of the screen).  This may require some monkeying with the double
buffer support in GTK.

-- 
           Summary: Component.print() and Component.printAll() does not
                    affect graphics parameter
           Product: gcc
           Version: 3.3.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: AWT
        AssignedTo: fitzsim at redhat dot com
        ReportedBy: myersj at gmail dot com
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org
 GCC build triplet: i686-pc-linux
  GCC host triplet: i686-pc-linux
GCC target triplet: i686-pc-linux


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16729


             reply	other threads:[~2004-07-26 23:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-26 23:20 myersj at gmail dot com [this message]
2004-07-26 23:23 ` [Bug AWT/16729] " fitzsim at redhat dot com
2005-08-24 19:22 ` [Bug awt/16729] " 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=20040726232019.16729.myersj@gmail.com \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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: link
Be 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).