[comp.sys.mac.apps] Excel 3.0 vs MacDraw II 1.1

torrie@cs.stanford.edu (Evan Torrie) (05/03/91)

  I've just unpacked my new copy of Excel 3.0, and set about testing
out its new charting features.  I seem, though, to have an
incompatibility when pasting from Excel 3.0 into MacDraw II.
  I select the graph, use the Copy Picture command,  but when I try to
paste it into MacDraw, all the text labels get scrunched up into a
single line near the top of the y axis, and all the columns in my
column chart disappear.
  It doesn't seem to matter whether I choose "Copy as shown on
screen", or "as shown when printed".  The same thing happens.
  I can paste the graph into the Scrapbook and it looks fine, and I
can also paste into Word, or PixelPaint without any problems.
  I tried exactly the same procedure with Excel 2.2, and it works
perfectly.  Is this an Excel 3.0 bug??


-- 
------------------------------------------------------------------------------
Evan Torrie.  Stanford University, Class of 199?       torrie@cs.stanford.edu   
Today's maxim:  All socialists are failed capitalists

benw@microsoft.UUCP (Ben WALDMAN) (05/07/91)

In article <1991May2.172853.22205@neon.Stanford.EDU> torrie@cs.stanford.edu (Evan Torrie) writes:
>
>  I've just unpacked my new copy of Excel 3.0, and set about testing
>out its new charting features.  I seem, though, to have an
>incompatibility when pasting from Excel 3.0 into MacDraw II.
>  I select the graph, use the Copy Picture command,  but when I try to
>paste it into MacDraw, all the text labels get scrunched up into a
>single line near the top of the y axis, and all the columns in my
>column chart disappear.

Well, since you can paste into every program BUT MacDraw, it seems to
be a MacDrawII bug, since MacDraw II parses PICTs (or so I would guess).

Anyway, I've just taken a look through the Excel source code, and can't 
understand why MacDraw would have any problems--we're just doing a MoveTo
and a DrawText.

If anyone at Claris is listening, you can give me a call at Microsoft,
and we can figure this out.

Ben Waldman
Excel Development Team
Microsoft
(206) 882-8080