🚀 go-pugleaf

Does anyone know of a problem in the CREATE.OBJECT function for embedded
charts in Excel 4.0 for Macintosh?  The gist of the problem is it doesn't
do what it's supposed to do when the selection is multiple (two discon-
tiguous columns, in this case).

The history of this is as follows:

I am developing an application in Excel for cross-development on Mac/Windoze.
The application creates a number of embedded charts.  In 3.0 (Mac),
CREATE.OBJECT worked fine; you SELECT (FORMULA.GOTO) the the data to plot
(XY chart) and then use COPY followed by CREATE.OBJECT (all of this is
happening on an add-in macro sheet adjunct to the worksheet).

In 4.0 Windoze version this also works fine (the screen graphics aren't
quite the same size but the effect is basically the same).  In 4.0 for
the MAC it works in one instance but not in the other.  The only difference
appears to be that the non-working instance is a multiple selection whereas
the working is not.  The symptom is that, without additional arguments, the
function creates a column graph instead of an XY as requested, but, even
with the extra arguments (all appropriate specified), the resulting XY
graph uses the wrong series values.  The X series gets left blank and the
Y series is what the X series is supposed to be.  In one instance, it seems
even more badly mangled although I haven't debugged it enough to get the
details (the result is that the y series ends up being a superset of the
desired X series).

Using the chart wizard tool on the tool bar with the same data works fine.
I could use the CHART.WIZARD function, but I'd like to maintain compatability
with 3.0 if possible.  I can presumably work around this with EDIT.SERIES, but
that's a crock.

I'm mainly asking to see if (a) anyone else has seen this, and (b) is there
a known fix.  For the moment, I'll assume I can work around it, I'd just like
to find a reasonably elegant fix as opposed to something like an EDIT.SERIES
crock. (e. g., specifying arguments more explicitly is acceptable as long
as it works the same in 3.0, but putting in what should be superfluous
functions is not).

Please reply by EMail if possible, but here is OK if not.-kby@caltech.alumni.edu