Thanks. Me too I got the same conclusions.
Anyway, I export the document as PDF with different page size using my own
procedure. That works.
Regards
-- Leonardo
> Da: Graham Cox
> Data: Thu, 13 Nov 2014 10:01:12 +1100
> A: Leonardo
> Cc:
> Oggetto: Re: Print Preview with different page size
>
The right solution is, as Fritz mentioned, to design your code to work
asynchronously. But for a quick-and-dirty solution to force a text field (or
any other UI) to show a change straight away is to include the redraw directly
yourself. This should not be done from a thread other than main howev
> On 13 Nov 2014, at 4:44 am, Leonardo wrote:
>
> Any solution?
Probably not, since printers are not physically designed to accommodate odd
mixes of paper sizes (other than initially selecting a source tray for a print
job). The design of the code reflects that.
--Graham
On 12 Nov 2014, at 2:58 AM, sqwarqDev wrote:
> Thanks for this Fritz. I think I get it. I need to get a clearer idea of how
> the run loop works. This isn't the first time I've been confused about why a
> line doesn't appear to return the result I expect before the next line
> executes. I supp
Jens,
> If you're using CoreData I'm not sure if you'll be able to fix your database
> schema, since presumably CoreData manages it and not you. So I'm not sure how
> you'd work around the problem. Good luck!
In fact, the Macports search engine is not, so I guess we’ll figure out a way
to fix
I can't succeed at printing/previewing a document containing several pages,
each one with different page size.
On the print panel, the preview page is the always fixed to the first page
size I set in the method printOperationWithSettings, using setPaperSize
NSPrintOperation *printOperation =
> On Nov 12, 2014, at 6:51 AM, Vincent Habchi wrote:
>
> the sqlite version installed on OS X machines has been bumped to 3.8.x in OS
> X 10.10. This apparently had the unfortunate side (or collateral) effect of
> plummeting performance of some requests (specifically, some Macports related
>
Folks,
the sqlite version installed on OS X machines has been bumped to 3.8.x in OS X
10.10. This apparently had the unfortunate side (or collateral) effect of
plummeting performance of some requests (specifically, some Macports related
database operations now take forever while they were fairl
> On 11 Nov 2014, at 23:01, Fritz Anderson wrote:
> -needsDisplay schedules a view’s -drawRect: for the next pass through the
> runloop. You’re putting your process to sleep at the OS level, so the runloop
> is suspended along with everything else.
>
> What you posted is evidently a minimal ca
