All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Wauck <alex.wauck@gmail.com>
To: "Petrie, Glen" <glen.petrie@eitc.epson.com>
Cc: printing-architecture@lists.linux-foundation.org,
	Till Kamppeter <till.kamppeter@gmail.com>
Subject: Re: [Printing-architecture] new cpd specs
Date: Thu, 9 Jul 2009 09:18:37 -0500	[thread overview]
Message-ID: <200907090918.51600.alex.wauck@gmail.com> (raw)
In-Reply-To: <ED4094DE5E8ACD4BBDACA6AD398E608F41885F@EEAEX03.us.epson.net>

[-- Attachment #1: Type: Text/Plain, Size: 937 bytes --]

> The question is providing a button to allow it.  This is a COMMON print
> dialog.  Therefore, the control should be there.  If an application does
> not (can not) support it, then the application elects to deactivate the
> button when the dialog is called.  In this specific example, the button
> may be deactivated if there is no clipboard content.  In addition, why
> should I have to go to another application (like Klipper) to print
> content I have access to.

What if the clipboard has data from another application?  It would be very 
strange to click "Print" in OpenOffice, select "Print from clipboard", and then 
have the printer spit out something from Firefox.

Alex

-- 
Public keys:
http://dragonfly.mediaservices.gac.edu/alex/keys/

()  ascii ribbon campaign - against html e-mail 
/\  www.asciiribbon.org   - against proprietary attachments

http://www.gnu.org/philosophy/no-word-attachments.html

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 835 bytes --]

  reply	other threads:[~2009-07-09 14:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-07 15:08 [Printing-architecture] new cpd specs Till Kamppeter
2009-07-07 20:12 ` Petrie, Glen
2009-07-07 20:28   ` Petrie, Glen
2009-07-09 13:51     ` Petrie, Glen
2009-07-09 13:56       ` Alexander Wauck
2009-07-09 14:09         ` Petrie, Glen
2009-07-09 14:18           ` Alexander Wauck [this message]
2009-07-09 14:25             ` Petrie, Glen
2009-07-08  9:24   ` peter sikking
2009-07-08  8:44 ` peter sikking

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=200907090918.51600.alex.wauck@gmail.com \
    --to=alex.wauck@gmail.com \
    --cc=glen.petrie@eitc.epson.com \
    --cc=printing-architecture@lists.linux-foundation.org \
    --cc=till.kamppeter@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.