Dplot jr 2 3 0 6 – 6 6 – ar


valid until 2018/1/23

Dplot jr 2 3 0 6

Dplot jr 2 3 0 6

Dplot jr 2 3 0 6

Dplot jr 2 3 0 6

Dplot jr 2 3 0 6

27.02.2018 – DPlot crashed if every point in one or more curves was outside the limits set with the Amplitude Limits menu command. Reading 4-byte unformatted data was broken with the addition of support for 8-byte unformatted data in version 2. For example 1 October 9:

Clean image dplot jr 2 3 0 6 you stick bastard

Dplot jr 2 3 0 6

What’s New?

1. 10In this version [ColumnsAre 0 ] results in the same behavior as not checking “Pick Columns to Plot” box: For bar charts, scatter plots, wireframes and waterfall plots, if antialiasing is turned off you’ll now get a smooth animation using the arrow keys.
2. 3 This is particularly useful for real-time applications, particularly after plotting many thousands of points. This limitation is not likely to change.http://softik.org/ccleaner-for-free-windows-10/ http://softik.org/ccleaner-for-windows-8-filehippo/You may also set the relative widths of bars with that command.

3. 10 Enter the e-mail address of the recipient Add your own personal message: http://softik.org/zte-max-xl-phone-reviews/ http://softik.org/zte-max-xl-accessories/If there was insufficient memory for the new array sizes, the old arrays might not have been restored and all values were set to 0’s.

User comments

Dplot jr 2 3 0 6

4. 8 Modified the dialog box so that it works as expected for line lengths greater than characters.Dplot jr 2 3 0 6Generally every curve on the plot would be smoothed.

5. 10 Though technically correct before, previous versions were visually confusing if, for example, the low extent was at some time other than midnight since the time was not shown.

6. 5 This worked fine unless the X axis used one of the calendar date formats.

7. 9 The Find Volume Under Surface command now also calculates the average Z for points above and below the specified base Z.

Dplot jr 2 3 0 6 mac antivirus free

Graph Software for Scientists and Engineers. Revision History Licensed users should sign up for the mailing list to receive instructions for downloading the free upgrade, or select Check for Updates on the Help menu within DPlot.

Gave up on trying to verify DPlot’s own digital signature with new, more dplot sha algorithm. Attempting to verify the signature under both Windows Vista and Windows XP resulted in errors that erroneously indicated the file had been tampered with.

If you have 2. The problem was related to updating to a more secure code-signing algorithm used by DPlot which is not supported by XP. The DPlot Add-in is now signed by an established certificate authority, which gets dplot a few Excel Trust Center settings.

For more information see the blog entry on the subject. DPlot might have crashed or at the very least presented nonsense values when opening file type N unformatted binary, 64 bit. The problem was due to mistakenly identifying the file as bit binary.

Improved saving metafiles of 2D contour plots with “Data points” checked on the Contour Options dialog. In previous versions the symbols were drawn point-by-point. This was fine for bitmaps, printouts, and displays, but resulted in very large metafiles because of the “resolution” of dpi.

Limits on frequencies in the Filter command were incorrect for all time units other than seconds. If you used the Reorder Curves command on a bar chart with multiple data sets, the fill styles were not shifted along with the corresponding bar s.

The specified font color for the legend in 3D plots was ignored and was always black. If you attempted to use the Differentiate a Curve command on a plot that had no curves with monotonically increasing X values, DPlot correctly refused to perform the command, but didn’t clean up properly and broke subsequent attempts to run most commands that displayed a list of curves.

Text notation button text is now saved to and restored from preference files. Added “Select all” and “Deselect all” options to the Combine Curves command. The frequency setting for Error bars was ignored for bar charts.

Reference line values entered with Time of day fractional days number format for the associated axis were interpreted incorrectly. Internally the value was treated as whole number hours rather than fractions of a day.

The “Sort on X” option of the Combine Curves command did not work properly in recent versions if you checked the “Keep originals” box. The downside to this change is that clipping may now occur, and this may require another change.

Reading 4-byte unformatted data was broken with the addition of support for 8-byte unformatted data in version 2. The Label Points command had a few quirks when working with hidden curves. List Peaks did not report the correct mean or number of points for “curves” consisting of a single point.

Added a “Date separator” entry to the General Options dialog. This entry might be important for German users or for users from any other country where the default date separator is a ‘. DPlot is a bit smarter about re-allocating arrays for unformatted data, both 4- and 8-byte files.

In previous versions when it was found that the arrays were of insufficient size, DPlot used the power of 2 greater than or equal to the required size. Since the required size was known, in many cases this was overkill – particularly for millions of points.

In this version DPlot will size the arrays to the exact size needed. In many cases this will make the difference in whether DPlot can successfully read the file or not. Another change fixes a bug that under some circumstances might have led to a complaint about being unable to allocate memory for curves, though the file contained only one data set.

Strangely, this bug has been present from day 1 but it is only recently that anybody has noticed it. In previous versions of DPlot, when printing if you specified more than 1 copy you’d actually get the square of that number rather than the specified number.

The problem was that DPlot was looping through that number of copies, and for each loop the printer driver was also printing that number of copies. This should have been done years ago.

Unformatted binary bit is identical to the “Unformatted binary” type except that it saves data to bit 8-byte double-precision floating point values rather than 4-byte single-precision values.

Curve labels for plots using the Amplitude Limits feature might not have been aligned properly. This worked, but line widths resulting in a calculated pen width of 1 pixel on most systems 0.

The intent is to offer the last folder saved to as the default, which this version and those prior to 2. When using the Zoom toolbar button or when zooming by dragging-and-clicking assuming “Click and drag to zoom” under the General Options command is checkedyou can restrict zooming to the X direction by pressing the Ctrl key or to the Y direction by pressing the Shift key.

Whether using dplot toolbar button or clicking-and-dragging, the key must be pressed and held before the action is initiated. This change necessitated a change in restricting the zoom rectangle to a square.

This omission was an oversight. Programmatically, you’ve always been able to control this setting with an AxisType command. Unfortunately this change broke SelectCurve -1which previously meant that all curves should be selected for subsequent operations.

SelectCurve -1 works as expected in this release. For those users who have previously used these modules, both now allow you to select which curve to operate on as well as specify whether the generated data should replace the input.

In previous versions the limits on the generated points were always shown as numbers, so a lack of precision might have resulted in the output extents being several seconds before or after the input extents.

This change only applies to XY plots. DPlot now uses version 3. The List Peaks within a Range command on random 3D points might have crashed on some versions of Windows due to an uninitialized data problem.

In some cases this “fix” might have dplot DPlot to crash. The down side to this change is that the DPlot menu will remain after removing the Add-In and until you restart that version of Excel.

For example LOG10 5. For random points this will replace the current data X, Y, and Z values with the clipboard contents. For points on a rectangular grid this will replace Z values with the clipboard contents, preserving X and Y.

This might be handy if you frequently produce 3D surface or scatter plots with complicated setups: DPlot crashed when saving DPlot files with notes longer than characters.

For large framed notes the rectangle surrounding the note might have been a bit too small or too large for vertical text. The Distance between points function for 3D surface plots with random points did not handle dragging the mouse to select points correctly.

There was a problem when reallocating arrays for XY plots with existing curves. If there was insufficient memory for the new array sizes, the old arrays might not have been restored and all values were set to 0’s.

There was a goof in the new Spline Fit dialog that caused the plugin to always operate on either the first or second curves, regardless of what selection you made in the plugin’s dialog box. Fixed a problem that has always existed for Generate plugins but only became noticeable with the last release’s inclusion of the Spline Fit plugin: If you set the “Number of points per segment” to a value large enough that DPlot could not allocate enough memory to accomodate that new curve e.

The result of this was that subsequent calls to that plugin would bypass the dialog box where you entered “Number of points per segment”, because the plugin thought this was a subsequent call after successfully reallocating arrays.

Added a Spline Fit function to the Generate menu. This operates in much the same way the Equal Intervals command with the Cubic Spline method does, but allows for input that loops back in X – is not a function, in other words.

Thanks to Erik Larson for the code. Added an option to the Histogram command to plot the frequency of a given bin rather than the count. Text and arrows for point labels that were copied to the clipboard may have been incorrectly placed with standard as opposed to enhanced metafiles.

A roundoff error in axis label placement for 2D surface plots might have resulted in the last label being omitted. This might be useful for very noisy data. Added a “Number of points” option to the “List Peaks” function.

Curve labels might had added uneccessary white space to the right side of a plot. With 2D views of contour plots of randomly-spaced 3D points, the legend might have been clipped in a copied bitmap produced by Copy Picture.

The “More Curve Fits” function might have crashed with some equation forms if you selected a curve to fit that contained a single data point. In this release those “curves” are not selectable. If the original document contained any notes and you performed any operation on the generated document’s data, then the Undo function did not work properly.

Generally on a Redo all X and Y values were set to 0’s. DPlot crashed when zooming in, then out, with the mouse wheel while pressing the CTRL key restricting zooming to the X direction if the plot included multiple Y axes.

Others may follow in a future release. The ZGrid command of the Excel Add-In is now much more efficient when you simply select column headings rather than the rectangle containing your data. And it now will correctly interpret evenly-spaced Y values when you select column headings and send the data to DPlot as points on a rectangular grid, rather than randomly-spaced points.

This is important if your goal is to produce 3D bar charts. This is primarily useful for those tracking stock prices. This is mostly a matter of convenience to those who crash cars for a living: Extents for scales using “Calendar Date” number formatting are now rounded to the nearest integer nearest day.

Though technically correct before, previous versions were visually confusing if, for example, the low extent was at some time other than midnight since the time was not shown. The setup program now copies examples.

Previous versions of the Excel Add-In for DPlot might have caused bit Excel to crash after successfully creating a plot. Changing colors in an XY plot with no other changes did not result in prompting you to save the plot when it was closed.

If you erased a hidden curve, the hidden flag was not reset. If you then performed some operation that created a new curve which filled the slot occupied by the previously erased curvethe new curve was hidden.

If you have a GPS device that records heartrate and exports to GPX but heartrate is not supported by this plugin, of course let us know.

Pobierz dplot jr 2 3 0 6 agosto

Tab alignment in text notes did not work properly in lines containing control codes subscripts, underline, etc. At least for now, I’ve given up on compressing executables. This bug did not effect dragging a file onto an open DPlot window or opening it with the Open command on the File menu. DPlot does a much better job with saving high resolution images, particularly with plots for which the legend or a text note has been moved well outside the extents of the plot. Also added a 0 parameter to Preserve3DScaleFactor to turn this feature off.

Dplot jr 2 3 0 6 online security plugin

This was fine for bitmaps, printouts, and displays, but resulted in very large metafiles because of the “resolution” of dpi. Limits on frequencies in the Filter command were incorrect for all time units other than seconds.

If you used the Reorder Curves command on a bar chart with multiple data sets, the fill styles were not shifted along with the corresponding bar s. The specified font color for the legend in 3D plots was ignored and was always black.

If you attempted to use the Differentiate a Curve command on a plot that had no curves with monotonically increasing X values, DPlot correctly refused to perform the command, but didn’t clean up properly and broke subsequent attempts to run most commands that displayed a list of curves.

Text notation button text is now saved to and restored from preference files. Added “Select all” and “Deselect all” options to the Combine Curves command. The frequency setting for Error bars was ignored for bar charts.

Reference line values entered with Time of day fractional days number format for the associated axis were interpreted incorrectly. Internally the value was treated as whole number hours rather than fractions of a day.

The “Sort on X” option of the Combine Curves command did not work properly in recent versions if you checked the “Keep originals” box. The downside to this change is that clipping may now occur, and this may require another change.

Reading 4-byte unformatted data was broken with the addition of support for 8-byte unformatted data in version 2. The Label Points command had a few quirks when working with hidden curves.

List Peaks did not report the correct mean or number of points for “curves” consisting of a single point. Added a “Date separator” entry to the General Options dialog. This entry might be important for German users or for users from any other country where the default date separator is a ‘.

DPlot is a bit smarter about re-allocating arrays for unformatted data, both 4- and 8-byte files. In previous versions when it was found that the arrays were of insufficient size, DPlot used the power of 2 greater than or equal to the required size.

Since the required size was known, in many cases this was overkill – particularly for millions of points. In this version DPlot will size the arrays to the exact size needed.

In many cases this will make the difference in whether DPlot can successfully read the file or not. Another change fixes a bug that under some circumstances might have led to a complaint about being unable to allocate memory for curves, though the file contained only one data set.

Strangely, this bug has been present from day 1 but it is only recently that anybody has noticed it. In previous versions of DPlot, when printing if you specified more than 1 copy you’d actually get the square of that number rather than the specified number.

The problem was that DPlot was looping through that number of copies, and for each loop the printer driver was also printing that number of copies. This should have been done years ago.

Unformatted binary bit is identical to the “Unformatted binary” type except that it saves data to bit 8-byte double-precision floating point values rather than 4-byte single-precision values. Curve labels for plots using the Amplitude Limits feature might not have been aligned properly.

This worked, but line widths resulting in a calculated pen width of 1 pixel on most systems 0. The intent is to offer the last folder saved to as the default, which this version and those prior to 2.

When using the Zoom toolbar button or when zooming by dragging-and-clicking assuming “Click and drag to zoom” under the General Options command is checked , you can restrict zooming to the X direction by pressing the Ctrl key or to the Y direction by pressing the Shift key.

Whether using the toolbar button or clicking-and-dragging, the key must be pressed and held before the action is initiated. This change necessitated a change in restricting the zoom rectangle to a square.

This omission was an oversight. Programmatically, you’ve always been able to control this setting with an AxisType command. Unfortunately this change broke SelectCurve -1 , which previously meant that all curves should be selected for subsequent operations.

SelectCurve -1 works as expected in this release. For those users who have previously used these modules, both now allow you to select which curve to operate on as well as specify whether the generated data should replace the input.

In previous versions the limits on the generated points were always shown as numbers, so a lack of precision might have resulted in the output extents being several seconds before or after the input extents.

This change only applies to XY plots. DPlot now uses version 3. The List Peaks within a Range command on random 3D points might have crashed on some versions of Windows due to an uninitialized data problem.

In some cases this “fix” might have caused DPlot to crash. The down side to this change is that the DPlot menu will remain after removing the Add-In and until you restart that version of Excel.

For example LOG10 5. For random points this will replace the current data X, Y, and Z values with the clipboard contents. For points on a rectangular grid this will replace Z values with the clipboard contents, preserving X and Y.

This might be handy if you frequently produce 3D surface or scatter plots with complicated setups: DPlot crashed when saving DPlot files with notes longer than characters. For large framed notes the rectangle surrounding the note might have been a bit too small or too large for vertical text.

The Distance between points function for 3D surface plots with random points did not handle dragging the mouse to select points correctly. There was a problem when reallocating arrays for XY plots with existing curves.

If there was insufficient memory for the new array sizes, the old arrays might not have been restored and all values were set to 0’s. There was a goof in the new Spline Fit dialog that caused the plugin to always operate on either the first or second curves, regardless of what selection you made in the plugin’s dialog box.

Fixed a problem that has always existed for Generate plugins but only became noticeable with the last release’s inclusion of the Spline Fit plugin: If you set the “Number of points per segment” to a value large enough that DPlot could not allocate enough memory to accomodate that new curve e.

The result of this was that subsequent calls to that plugin would bypass the dialog box where you entered “Number of points per segment”, because the plugin thought this was a subsequent call after successfully reallocating arrays.

Added a Spline Fit function to the Generate menu. This operates in much the same way the Equal Intervals command with the Cubic Spline method does, but allows for input that loops back in X – is not a function, in other words.

Thanks to Erik Larson for the code. Added an option to the Histogram command to plot the frequency of a given bin rather than the count. Text and arrows for point labels that were copied to the clipboard may have been incorrectly placed with standard as opposed to enhanced metafiles.

A roundoff error in axis label placement for 2D surface plots might have resulted in the last label being omitted. This might be useful for very noisy data. Added a “Number of points” option to the “List Peaks” function.

Curve labels might had added uneccessary white space to the right side of a plot. With 2D views of contour plots of randomly-spaced 3D points, the legend might have been clipped in a copied bitmap produced by Copy Picture.

The “More Curve Fits” function might have crashed with some equation forms if you selected a curve to fit that contained a single data point. In this release those “curves” are not selectable.

If the original document contained any notes and you performed any operation on the generated document’s data, then the Undo function did not work properly.

Generally on a Redo all X and Y values were set to 0’s. DPlot crashed when zooming in, then out, with the mouse wheel while pressing the CTRL key restricting zooming to the X direction if the plot included multiple Y axes.

Others may follow in a future release. The ZGrid command of the Excel Add-In is now much more efficient when you simply select column headings rather than the rectangle containing your data.

And it now will correctly interpret evenly-spaced Y values when you select column headings and send the data to DPlot as points on a rectangular grid, rather than randomly-spaced points. This is important if your goal is to produce 3D bar charts.

This is primarily useful for those tracking stock prices. This is mostly a matter of convenience to those who crash cars for a living: Extents for scales using “Calendar Date” number formatting are now rounded to the nearest integer nearest day.

Though technically correct before, previous versions were visually confusing if, for example, the low extent was at some time other than midnight since the time was not shown.

The setup program now copies examples. Previous versions of the Excel Add-In for DPlot might have caused bit Excel to crash after successfully creating a plot. Changing colors in an XY plot with no other changes did not result in prompting you to save the plot when it was closed.

If you erased a hidden curve, the hidden flag was not reset. If you then performed some operation that created a new curve which filled the slot occupied by the previously erased curve , the new curve was hidden.

If you have a GPS device that records heartrate and exports to GPX but heartrate is not supported by this plugin, of course let us know. In particular this might make a difference for you when using the Directory 1 macro command.

A SelectCurve command prior to an EditSmooth command did nothing. Generally every curve on the plot would be smoothed. In all previous versions if you used a text placeholder for a parameter in a macro command, e.

For example 1 October 9: In this release up to 16 significant figures are used in this situation. DPlot crashed if every point in one or more curves was outside the limits set with the Amplitude Limits menu command.

On an XY plot if minor grid lines were used on the Y axis and the minor grid lines used a different color than the major grid lines, DPlot would redraw the major grid lines on the X axis so that they would not be obscured by the minor Y lines.

This worked fine unless the X axis used one of the calendar date formats. In that case the major lines were redrawn at a fixed interval, e. This bug has been present for over a year but only recently discovered by user PaulT.

Minor change to reading DPlot files: This differs from previous versions that tended to use the setting from the last plot that was opened. This release doesn’t use a zip file.

You might have run into this when, for example, creating a plot from scratch with the Edit Data command and hitting Cancel rather than OK. You’d be left with a picture of the Edit Data dialog and a depressed Cancel button.

The plot in this case was not redrawn, since there was nothing to draw. If attempting to read one of these files DPlot would not present an error message, but neither would it produce a plot.

The new feature of allowing shaded bands and contour lines in a 2D view of a surface plot required 1 new GDI object that was not properly destroyed after painting the plot. In general this bug would only be an issue for developers driving DPlot from another application when that app might produce many hundreds of 2D surface plots in any one session.

Reset the expiration date check for the trial version. If you’ve previously used the trial you’ll be able to use this version for 30 days. The fix for zooming in on logarithmic scales only worked correctly for values greater than 1.

There were two problems associated with version 2. With the default extents use as much of the display as possible this might have resulted in numbers being clipped at the left edge of the screen and the right edge if multiple axes were used.

If selected, black lines are drawn at the boundaries between shaded bands. These lines are optionally labeled in the same way that “Contour lines” plots are. For 3D points on a rectangular grid drawn in 2D, amended the interpolation scheme for “Shaded bands”.

This was done to accommodate the above “Both lines and shades” option. In previous versions shaded bands used a bilinear interpolation scheme, while contour lines broke each grid rectangle up into 4 planar triangles with the center point being the average of the 4 corners.

The bilinear method generally produced smoother-looking contours for sparse data, but that smoothness wasn’t based on any insight into the data and so probably wasn’t justified. In any case the bands did not match up with contour lines; in this version they do.

Added a “Minor line width” option for 2D surface plots. You can set the interval for “major” lines using the “Major lines every” control. As before, labels will be drawn on lines at this interval if the “Label every major line” box is checked.

Note that this may mean that portions of the plot will be clipped when using this option. For best results first select viewing angles that will make the plot take up the largest portion of screen space – typically this will be at azimuths of 45, , , or degrees.

Added right-click menu items for 3D surface plots in a 3D view. You can now quickly switch to a surface plot, wireframe plot, and for 3D points on a rectangular grid to a waterfall plot or bar chart.

You can now control the size of the symbols used in surface plots when “Data points” is checked on the Contour Options dialog. On 2D views, all plot types, if you used the Print Caption option on the Text menu to display the plot filename in the lower right corner of the plot, that caption might have overlapped the numbers along the X axis.

For logarithmic scales on XY plots, DPlot would not allow you to zoom in to extents that were not 5 or 10 times some power of In this release you can zoom in to extents with 2 significant figures.

DPlot did not correctly parse clipboard text with a date in the first column, time in the second column. In this version pasting this data from the clipboard behaves the same way that reading that data from a file would: For example 1E-9 might have been displayed as 1.

If you used a single custom contour level of 0 with surface plots and re-opened the Contour Levels dialog, DPlot crashed with a division by 0 error. In previous versions DPlot automatically cropped metafiles and enhanced metafiles, eliminating excess white space.

In most cases of course this was a good thing. But when driving DPlot from another program, retrieving a metafile from DPlot and setting that picture to be the background of a picture frame in that application, the resulting plot might not have had the expected aspect ratio.

This was particularly noticeable with polar plots, which might not have been circular. In this release you or rather your program will get the metafile it asks for, including white space.

Amended the VB btest4 and C ctest4 demo programs distributed with DPlot Jr to request a metafile size more in synch with the picture frame dimensions. Previous versions forced the width to 5 inches and the height was set proportional to the width, according to the relative frame dimensions.

The only trouble was that DPlot forces both the width and height to be at least 3 inches, so wide frames would end up producing distorted plots. In this release the document window background is not erased when updating the plot.

So you can spin a 3D view around without a lot of annoying screen-flashing. For bar charts, scatter plots, wireframes and waterfall plots, if antialiasing is turned off you’ll now get a smooth animation using the arrow keys.

Surface plots are a bit sluggish because DPlot draws every individual pixel. Another change related to the view angle keyboard shortcuts: A change in behavior for 3D bar charts: If “Borders” on the Contour Options dialog is unchecked, then bars will not be outlined in black.

This change was made primarily for viewing bar charts at an elevation angle of 90 degrees top-down where the black lines might have overwhelmed the plot for more than a thousand or so data points.

DPlot does a much better job with saving high resolution images, particularly with plots for which the legend or a text note has been moved well outside the extents of the plot. If you elected to crop whitespace in the image, those text entries might have been cropped or left completely out of the image.

In at least some cases attempting to save a high resolution image with text objects well to the left or above the plot might have resulted in a crash. Improved placement of axis labels and numbers on 3D views.

When using “Symbol sizes in Z units” for 3D scatter plots, DPlot erroneously applied the Z scale factor to the symbol sizes twice. For very small scale factors this error might have caused an integer overflow and subsequent crash.

The legend entries for median-based 1D box-and-whisker plots were fouled up starting with version 2. Axis labels were drawn in the incorrect location on 3D views with an elevation of 0 degrees.

Not documented anywhere but here yet: This feature of course works best with simple plots: In the Symbols dialog for 3D scatter plots, if you selected the new cube symbol introduced with version 2.

The new functionality of the Preserve3DScaleFactor command namely, keeping the axis of rotation at a fixed spot on the plot introduced with version 2. This was particularly noticeable in animations using Wingding symbols.

The problem was due to the fixed location in the plot that was used to obtain a scale factor for the symbols. Before perspective projection was added, the location where that measurement was taken was irrelevant because any distance in the Z direction was the same everywhere.

Generally this resulted in appending 0,0,0 triplets to one or more sets. Bar charts may now be selected with the Contour Options command for 3D views of Z values on a rectangular grid.

You may also set the relative widths of bars with that command. Slightly altered the 3D projection method used by DPlot. In previous versions it was not possible to reliably back out a viewpoint from the azimuth and elevation when perspective projection was used.

This wasn’t a serious weakness with surface plots but led to incorrect depth-sorting problems with 3D bar charts. Added a cube symbol for 3D scatter plots.

Unlike other symbols the cube is truly 3D, and is drawn with respect to your perspective settings. Programmatically that symbol type may be selected with [SymbolType curve , ].

This symbol will only be used if Symbol sizes in Z units is checked on the Symbol styles dialog box. Added droplines for 3D scatter plots. Lines may be in the symbol color or black, and you have control over the line width.

Changed the behavior of the Preserve3DScaleFactor command. This command has always been useful for producing sequences of bitmap images to import into movie-making applications like Windows Movie Maker.

But in previous versions no attempt was made at fixing the location of the center of the graph, so frames tended to jump around the screen a bit during animations. In this release Preserve3DScaleFactor preserves the scaling and the extents of the current frame and re-uses those values in all subsequent frames, so that the graph’s center of rotation will be in the same place in all frames.

Also added a 0 parameter to Preserve3DScaleFactor to turn this feature off. List Peaks and List Peaks within a Range previously included data points outside the range specified with the Amplitude Limits command.

This version ignores those points. Selecting points by clicking on the plot with the Distance from command did not work well with 3D views if a perspective projection was used.

In previous versions the perspective value was loosely the distance from the viewpoint to the center of the box bounding the plot. Although this worked fine, determining a good value for one plot had no relevance to other plots with different extents.

In this release the perspective value is a ratio of one-half the box diagonal. A value of 1, then the minimum produces a very distorted view with the viewpoint on the smallest imaginary sphere that surrounds the plot.

Most surfaces will look best with a perspective value of 2 or more. This change requires ignoring perspective values saved to DPlot files with version 2. Programmers who used the perspective setting with a ContourView command will need to make changes to their code.

Added 3D bar charts. This feature is currently only available via macro command and will likely be added to the user interface in the next release. This limitation is not likely to change.

The following sequence of macro commands will produce a 3D bar chart: Want to be informed of updates? Add this link to your RSS feed reader:. This will of course change once this feature becomes “official”.

Comments and suggestions are of course welcome. An uninitialized data problem related to version 2. Minor changes to the Contour Options and Scatter Plot Options dialogs pertaining to new perspective projection feature.

Programmers see the updated ContourView command. The Polynomial Curve Fit command generated a curve with arbitrary line and symbol types. In this version the newly-generated curve will use solid line segments and no symbols.

Starting with version 2. This made it impossible to scale mouse position to plot space unless, of course, your program knew the scale factor used by DPlot. This was done to make the triangulation routine more efficient for surface plots, but the sorting was also done for scatter plots.

There is no logical reason to do this for scatter plots. And if you chose to draw line segments between data points, the lines would of course not be drawn between the points you expected.

Bubble plot points were clipped against the extents of the primary Y axis, even if Multiple Axes were used and the graph was associated with the second Y axis.

If Degrees, Minutes, Seconds or Degrees, Minutes number format was used, DPlot did a poor job of handling negative values between 0 and -1 degree, both on input and output. A roundoff error might have resulted in the upper X extent shifting right every time a plot was redrawn if Calendar Date number formatting was used.

Fine so far, but when scrolling through the list of labels or clicking OK, DPlot attempted to read a date and time from that text box, found only a time, and set the date to 0 Dec 31, Thanks Jon Canale for pointing out the problem.

If you used Reference lines with the “Label” set to draw the reference line label in the plot legend, the label might have been replaced by the previous legend entry.

Thanks to Richard Swaim for pointing out the problem. The added support for alternate decimal symbols in 2. In all other functions that stored previously-used equations, the equation was not rewritten using the new rules related to a comma decimal symbol.

So you might have encountered a syntax error on an equation that previously worked as expected. All of the changes to point labels in version 2. The label location if expressed in plot coordinates rather than an offset was rounded to the nearest integer.

And if you had multiple labels on a plot, scrolling through the list of labels did not properly update the other fields on the dialog. So if you had labels you might have ended up with identical labels just by scrolling through the list.