Hi Again
I haven't heard anything from my initial question yet, but .. the first issue, of saving to an RTF file, has been solved (years ago, as it happens).
To save the contents of an EV_RICH_TEXT widget, use <widget>.save_to_named_path (<path>).
I guess that might have been obvious to some - though not to me at the time, apparently :)
The save-to-a-file logic is implementation-specific, but it strikes me that a minor, and yet rather nifty, enhancement might be to break that routine into a buffer generator and a save-buffer-to-file sort of thing.
Armed with a buffer and a file descriptor, it would then be easy enough to send the buffer's RTF contents to a socket or pipe.
This still does not address the print-from-a-widget, or frankly the print-at-all challenge. The print dialog (EV_PRINT_DIALOG) is easy enough to instantiate and show, but it has no context, so to speak. It does have a 'context' feature, but that doesn't seem (to me) to relate to anything resembling a get-this-to-the-selected-printer functionality. The missing part seems to be connecting the content to the printer. Having the content as a buffer, and the ability to send the buffer the printer object would be very nice indeed.
I'll readily concede that I could have missed something, perhaps an obvious something, but I have yet to find it. Any and all suggestions welcomed
Thanks
R