Just a suggestion, when I encountered this problem and got around it by having my FOX application generate pdf files, and then launching acrobat reader for a "print preview" functionality. This worked really well.
In my case, the output was pretty simple so I created ps files and used ps2pdf, but there are plenty of good APIs for generating pdf files, and many of these are free and/or open source, and can handle images, embedded fonts, etc.
----- Original Message ----
From: Tony Aldrich <tony.aldrich@...>
To: Jeroen van der Zijp <jeroen@...>; FOX Users <foxgui-users@...>
Sent: Friday, January 27, 2006 1:18:57 AM
Subject: Re: [Foxgui-users]Printing question
It sounds encouraging. It must work at least somehow, we are not talking about perfectness (as I hastily said in previous mail).
We all understand that you are very busy.
I want to ask only about what are you going to do and how? How can we help?
Is there any concept of how to do this?
I encountered with a need to have the same layout mechanisms on paper as it is on screen.
I mean all thouse packers, matrix , vertical and horizontal frames, the same layout flags to
put into them some text, images an so on. How we can unify screen and paper ways of data representation?
[For now I made some form of quick carbon (really not a clever way): place all children I need on invisible window and then ask about it's size to place it directly on printer canvas.]
But I think we have to break out layout calculations to use them in different places.
The same could be said about basic functions needed everywhere and pasted in many places instead of calling them like
drawMultilineTextIconChain with option of Wrap words and so on.
What about breaking things into piecies?
Eventually, I hope to get printing going. Maybe the infrastructure
for printing will improve [because its really the poorness of the
underlying infrastructure, not FOX itself, thats the problem].