[open-beos-printing] =?iso-8859-1?Q?Re: Undocumented transport add-ons init=5Ftransport() =behavior!??=
- From: Michael Pfeiffer <michael.pfeiffer@xxxxxxxxx>
- To: open-beos-printing@xxxxxxxxxxxxx
- Date: Tue, 21 May 2002 21:17:36 +0000
>
>Quoting :
>> Hmm, I don't know if this is the official way, but I have found a
>> possibility
>> to work around that problem (see repository).
>
>Yep, I was thinking about this workaround, but it assert that
>the transport add-on in use is "Print To File".
I don't think so. If the fTransport is not inherited from BFile or is
NULL then dynamic_cast<BFile*>(fTransport) should return NULL
and the test if it is a invalid file is not made.
>While it's not a big issue with PDF Writer, it is one
>with all others print drivers, Canon BubbleJet for one.
>And as OpenBeOS "Print To File" print_server transport add-on
>writer, it's sad I can't see how it should works...
Don't understand the problem?
>How I hate closed-source sometimes!
>
>So, anyway, time to anew PDF Writer release, maybe?
>Or what's still on the TODO-list before?
TODO list:
open: documentation
open: transparency for patterns
open: further tests have to be made & bug fixes if necessary:
open: scaling and translation
open: position and size of bitmaps
done: clipping to "stroked path"
done for x86: update of PDFlib to 4.0.2
So some points are still open; I will make "transparency for
patterns" and the pdflib.so for PPC until Sunday. From
my side it would then be ready. Don't know how the state
of the documenation is and if it is required to have one.
- Michael
Other related posts:
