We have examine, the plug-in xmChart 3.1, for making graphs and want to use it in our FM application. It’s great that’s for sure ! But what we miss is a summary of the effect of all possible parameters.

We have de original manual with all commands and parameters but isn’t not always clear what thy do.

Is there a simple example file where you can put in the variable’s (parameters) in fields?

PL keep me informed so we can compare notes !!!

There should be a file with the download called XmGallery, it is loaded with examples of different types of graphs and formats.

Yes we know the file. But the whole definition of the graph is in one field, we are looking for a file where we can fill in all diferent parameters in diferent fields.

@rjen

... work out what all the paramaters are, define the fields you want to enter parameters in and then join them all together in one calculation field

e.g. field1 & "?=1233" & field2 & "..."

or whatever the correct syntax is.

FYI: this is not a trivial process. Some chart options are only relevant for certain types of charts, so the calc requires case()'s to append those options if needed.

I've built such a file, giving the user control of a wide variety of options for their charts. Unfortunately, I'm not at liberty to share it.

Hi Ender,

Thats exactly what I mean, we face the here same problems

Can we buy this file, or send me a locked file???

Of can you help me out in any way.... :thankyou:

... stop being lazy, make yourself a custom function. It doesn't take more than a couple of days.

A custom function wouldn't be appropriate here. The issue is putting a user interface on a large number of settings to customize the values sent to the charting plug-in. For example, in my solution there's something like 30 different user selectable settings, including chart size, chart type, border thickness, x-range, y-range, minor axis ticks, major axis ticks, minor axis tick color, major axis tick color, series symbols, series colors, series line thickness, legend position, legend border, legend font/size, title font/size, subtitle font/size, series label text, series label font/size. These fields are put together in a "charting module" where the fields can be adjusted and the chart refreshed with the new settings.

For these to be customizable, they should be fields that can be manipulated by the user. Part of the trick for doing this right is deciding which fields are globally stored and only retained for the session, and which might be useful to store for future reports by the user, maybe storing them in the User table. For automated reports, some of those fields can be automatically set by a calling script (like the Chart Type, Title, and Sub Title), where other fields could start with any previously stored settings that the user has set (like the colors or symbols for each series).

So the process is that each report assembles the data series in strings (x-axis values or x-y coordinates and the x-axis labels), then some of those default values and the strings are passed to the charting module for customization. If the user wishes to customize something on a chart, they need only adjust the settings in the charting module and hit a refresh button (there's no need to reassemble the original data strings). A charting module like this has the advantage of giving some user control over the look of the chart, and centralizes the customization in one place for all chart-related reports.

Oh right, i thought this was a "I am a developer and am too lazy to work out what all the parameters for graph x that i want to produce for my users are" issue.

My bad, i apologize.