🚀 go-pugleaf

In article <598@eutrc3.UUCP> rcbamw@eutrc3.UUCP (m.waucomont) writes:
>When it was finally finished, I wanted to see the result on paper, so
>I chose 'page setup' to see what was inthere. [...]
>I chose 72dpi and clicked 'OK'.
>THE STUPID THING STARTED REDRAWING THE GRAPH!!!!
>(Would it be a stupid idea to BitCopy the area where the dialogue box
>will apear into an array, then display the dialogue box, remove it when
>done and BitCopy the array back to the window? Would have saved me
>another 2 minutes)

Not to argue with the other points (I don't have WingZ), but this is definitely
a Terrible Bad Awful Idea, and the Apple Thought Police will lock you up if
you do this.

Actually, it can break a variety of things, most of them obscure, but is
more likely to fail in the future. Robert Woodhead wrote an article about
tricks for programming the Mac, about two-three tears back, which wound up
on the Arpa Info-Mac group (and maybe here too), wherein he recommended
doing this. There were many responses about how this wouldn't work in certain
circumstances.

I won't go into details (you can post to c.s.m.programmers if you want) but
for example, how would you handlea window that belonged to a different app
(there's this thing called MultiFinder, you know) which was MF-aware and
updated windows in the background? You can't.

---
Alexis Rosen
alexis@ccnysci.{uucp,bitnet}
alexis@rascal.ics.utexas.edu  (last resort)