On Sep 7, 2019, at 4:29 AM, Mark Waddingham via use-livecode
wrote:
>
> On 2019-09-06 21:10, Dr. Hawkins via use-livecode wrote:
>> On Aug 28, 2019, at 12:07 AM, Mark Waddingham via use-livecode
>> wrote:
>>> On 2019-08-27 17:24, Dr. Hawkins via use-livecode wrote:
>>> I'm not entirely clear
On 2019-09-06 21:10, Dr. Hawkins via use-livecode wrote:
On Aug 28, 2019, at 12:07 AM, Mark Waddingham via use-livecode
wrote:
On 2019-08-27 17:24, Dr. Hawkins via use-livecode wrote:
I'm not entirely clear what Monte meant by 'print to pdf directly' in
one
of those comments... The 'print
On Aug 28, 2019, at 12:07 AM, Mark Waddingham via use-livecode
wrote:
>
> On 2019-08-27 17:24, Dr. Hawkins via use-livecode wrote:
>> I’ve seen references, even in the bug report, to “directly” printing
>> to pdf from a widget.
>
> I'm not entirely clear what Monte meant by 'print to pdf
> On 28 Aug 2019, at 5:07 pm, Mark Waddingham via use-livecode
> wrote:
>
> I'm not entirely clear what Monte meant by 'print to pdf directly' in one
> of those comments..
Ah I was talking about printing the PDF file directly. May have been before I
realised there needed to be overlaid LC
On 2019-08-27 17:24, Dr. Hawkins via use-livecode wrote:
I’ve seen references, even in the bug report, to “directly” printing
to pdf from a widget.
I'm not entirely clear what Monte meant by 'print to pdf directly' in
one
of those comments... The 'print to pdf' mechanism in the engine isn't
I’ve seen references, even in the bug report, to “directly” printing to pdf
from a widget.
My experience has been that it still reduces the pdf to screen resolution.
I still insist they the fact that the engine *renders* the pdf, rather than
including it, is a hard-core bug. I attached an
