Re: [fltk.development] fl_can_do_alpha_blending() [Library] r7363 - branches/branch-1.3/src

2010-03-31 Thread manolo gouy
Printing-wise, it works only on Mac as of today. My commit concerns WIN32. It consists in asking whether the printer in use can blend, do the blending if the answer is positive, and do a simple copy if it is negative. I think you wrote previously that some MSWindows pseudo printer could

Re: [fltk.development] fl_can_do_alpha_blending() [Library] r7363 - branches/branch-1.3/src

2010-03-31 Thread Albrecht Schlosser
On 31.03.2010, at 08:04, manolo gouy wrote: Printing-wise, it works only on Mac as of today. My commit concerns WIN32. It consists in asking whether the printer in use can blend, do the blending if the answer is positive, and do a simple copy if it is negative. I think you wrote previously

Re: [fltk.development] fl_can_do_alpha_blending() [Library] r7363 - branches/branch-1.3/src

2010-03-31 Thread manolo gouy
On 31.03.2010, at 08:04, manolo gouy wrote: Printing-wise, it works only on Mac as of today. My commit concerns WIN32. It consists in asking whether the printer in use can blend, do the blending if the answer is positive, and do a simple copy if it is negative. I think you wrote

Re: [fltk.development] fl_can_do_alpha_blending() [Library] r7363 - branches/branch-1.3/src

2010-03-31 Thread manolo gouy
manolo gouy wrote: I've fixed the transparency problem. It now fully works with XPS and does transparency to white background with PDF printer. I've seen your commit, but not tested yet. Just for curiosity: it looks as if the XPS printer device didn't return the expected value from

Re: [fltk.development] Is Fl_Clipboard_Writer a good idea?

2010-03-31 Thread MacArthur, Ian (SELEX GALILEO, UK)
Now we have our new Fl_Device class, I propose to add the new class Fl_Clipboard_Writer that would direct graphics requests to the clipboard (or pasteboard in Mac OS parlance). This would allow to copy to the clipboard any widget or any series of FLTK graphics requests. I think I do not

Re: [fltk.development] Is Fl_Clipboard_Writer a good idea?

2010-03-31 Thread Albrecht Schlosser
manolo gouy wrote: Now we have our new Fl_Device class, I propose to add the new class Fl_Clipboard_Writer that would direct graphics requests to the clipboard (or pasteboard in Mac OS parlance). This would allow to copy to the clipboard any widget or any series of FLTK graphics requests. I

Re: [fltk.development] Is Fl_Clipboard_Writer a good idea?

2010-03-31 Thread manolo gouy
Now we have our new Fl_Device class, I propose to add the new class Fl_Clipboard_Writer that would direct graphics requests to the clipboard (or pasteboard in Mac OS parlance). This would allow to copy to the clipboard any widget or any series of FLTK graphics requests. I think I do

Re: [fltk.development] Is Fl_Clipboard_Writer a good idea?

2010-03-31 Thread MacArthur, Ian (SELEX GALILEO, UK)
I can also see that we currently don't have support for putting graphics onto the clipboard. The only method that I know of is Fl::copy(const char *stuff, int len, int clipboard=0) to copy text. Though I suppose an image can be passed via a char* and a length. ;-) going off-topic

Re: [fltk.development] Is Fl_Clipboard_Writer a good idea?

2010-03-31 Thread MacArthur, Ian (SELEX GALILEO, UK)
In Mac OS and MSWindows, the clipboard can be routinely used to transfer graphical data between applications, in addition to transferring text data. These OSes have a standard format for that. In MSWindows, it's metafile; in Mac OS it used to be PICT and is now PDF. And the ICCM defines how

Re: [fltk.development] Is Fl_Clipboard_Writer a good idea?

2010-03-31 Thread manolo gouy
manolo gouy wrote: In Mac OS and MSWindows, the clipboard can be routinely used to transfer graphical data between applications, in addition to transferring text data. These OSes have a standard format for that. In MSWindows, it's metafile; in Mac OS it used to be PICT and is now PDF.

Re: [fltk.development] Is Fl_Clipboard_Writer a good idea?

2010-03-31 Thread imacarthur
On 31 Mar 2010, at 17:54, manolo gouy wrote: Nothing is ready for the X11 platform. That's where the question mark is. For X11 there are essentially two separate (but very similar) mechanisms to consider, the ICCM's Selection Buffer mechanism and the later XDnD mechanism. It is not so