Ian: I have added the new class Fl_Clipboard_Writer for Mac MSWin to
branch-1.3-Fl_Printer (after having updated it to the current 1.3).
Thus, you may add your stuff therein as well.
OK - my progress has been slow, I got distracted playing about with
making the clipboard work in my test app,
I look forward receiving that, because I'm not at ease for clipboard
and X11. Thanks so much.
OK - but it will probably be later rather than sooner, as I have a
few things to try and get done over the next week or two...
Ian: I have added the new class Fl_Clipboard_Writer for Mac
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 have that already in
On 31.03.2010, at 18:54, manolo gouy wrote:
My existing code is only for MSWindows and Mac OS X.
In essence, the system calls CreateEnhMetafile and CGPDFContextCreate
of each system return a graphics context (fl_gc). With that,
all graphics requests (all fl_XXX() functions) write to an
Because focus on releasing FLTK-1.3 is essential now,
I conclude that I will prepare an Fl_Clipboard_Writer class
as an MSWindows Mac OS-only add-on to FLTK-1.3 and put it=20
in the Bazaar.
This sounds like a good compromise.=20
Once we have a stable 1.3 out, we can merge this stuff
On 31.03.2010, at 18:54, manolo gouy wrote:
My existing code is only for MSWindows and Mac OS X.
In essence, the system calls CreateEnhMetafile and CGPDFContextCreate
of each system return a graphics context (fl_gc). With that,
all graphics requests (all fl_XXX() functions) write to an
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
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
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
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
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
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.
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
13 matches
Mail list logo
