Three unrelated questions about Graphics and Mathematica 5.2
- To: mathgroup at smc.vnet.net
- Subject: [mg75924] Three unrelated questions about Graphics and Mathematica 5.2
- From: Szabolcs <szhorvat at gmail.com>
- Date: Sun, 13 May 2007 05:53:05 -0400 (EDT)
- Organization: University of Bergen
1. There appears to be an inconsistency in how FullGraphics works. Example:
g = Plot[Sin[x], {x, 0, 10}, Prolog -> {Red}]
Show[FullGraphics[g]]
Is is possible to create an "expanded" Graphics object from g that
renders exactly like g itself? Or is the conversion done directly to
PostScript before displaying (so a full representation as Graphics is
never generated)?
2. How can one convert a Graphics3D object to 2D Graphics and preserve
the 3D axes? The axes are gone here:
gg = ParametricPlot3D[{Sin[x], Cos[x], 0}, {x, 0, 2Pi}]
Show[Graphics@gg, AspectRatio -> Automatic]
3. I see that Display sends its output to {"stdout"} by default, and
this output appears in the front end. Where can one find some
documentation about what format should this output have to show up
correctly in the front end? Is it possible to call an external
PostScript renderer to rasterise the graphics, but make the result show
up in the front end?
If yes, is it possible to make the front end call the external
rasteriser, and regenerate the bitmap, every time the graphics cell is
resized?
4. And a few questions about Mathematica 6: In v5.2 fonts were not
magnified together with other parts of graphics in the front end.
Therefore when the graphics were exported to a vector format (e.g. EPS),
the end result didn't look the same as in the front end. Has this been
solved in Mathematica 6?
Is it still possible to get the old-style PostScript graphics by
redefining $DisplayFunction to Display[$Display, #1] &?
What do 3D graphics look like when exported to a vector format? Do they
have the smooth mesh with generous spacing (as they appear in the front
end), or are they the same as in v5?
Unfortunately these things cannot be tried with the trial version
because Export is disabled. For some reason searching the documentation
for anything that is not the name of a built-in also fails with a
message that Export is disabled. (Why is Export needed for searching??)
Of course the online docs work fine.