<?xml version="1.0" encoding="iso-8859-1" ?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">

<channel>
    <title>DPlot Graph Software</title>
    <link>http://www.dplot.com</link>
    <description>DPlot Graph Software for Scientists and Engineers</description>
	<lastBuildDate>Sun, 07 Mar 2010 15:21:00 GMT</lastBuildDate>
	<language>en-us</language> 
	<copyright>Copyright 2001-2010 HydeSoft Computing, LLC.</copyright> 
	<managingEditor>David Hyde</managingEditor> 
	<webMaster>admin@dplot.com</webMaster> 
<image>
	<title>DPlot Graph Software</title> 
	<url>http://www.dplot.com/logo_small.png</url> 
	<link>http://www.dplot.com</link> 
	<width>141</width> 
	<height>45</height> 
	<description>Graph Software for Scientists and Engineers</description> 
</image>

<item>
	<title>Improved handling of CSV files</title>
	<link>http://www.dplot.com/revisions.htm#R2281</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2281"></a><h3>7 March, 2010<br>
	Version 2.2.8.1</h3>
	<ul>
	<li>Added a &quot;Expand constants in legend&quot; checkbox to the 
		<a href="http://www.dplot.com/help/index.htm?helpid_f_of_x.htm">Y=f(X)</a> and similar dialogs. If checked,
		constants (A,B,C,etc.) used in equations will be replaced with their corresponding numeric values in the
		legend (title in the case of 3D surfaces).<br>&nbsp;</li>

	<li>For surface plots from randomly-spaced data, DPlot does a better job of selecting which point the mouse is
		hovering over before displaying a popup note with that point's coordinates.<br>&nbsp;</li>

	<li>Improved handling of headings in saved CSV files for XY plots. In previous versions if there was only one
		curve, the heading was set to the Y axis label (which might have been blank) regardless of whether the 
		curve had a legend entry or not. In this version, when only one curve is present then (as before) the Y 
		axis label is used as the heading; if the Y axis label is blank then the corresponding legend entry is used.
		Similarly, if the X axis number format is dates and/or times and the X axis label is blank then DPlot makes 
		a number-format related decision about an appropriate label: &quot;Date&quot;, &quot;Date/Time&quot;, or
		&quot;Time&quot;.<br>&nbsp;</li>

	<li>Right-clicking along the Y axis on an XY plot in previous versions allowed you to set the upper/lower limits of the
		Y scale, but only for the primary Y scale regardless of which side of the plot you clicked on. In this version if you
		are using two independent Y axes and click on the right side, you are given the option of changing the extents of the
		right Y axis. Note that this may not necessarily lead to the expected results: DPlot will always try to find a reasonable
		tick mark interval such that each Y axis has the same number of intervals.<br>&nbsp;</li>

	<li>You can now set the color of minor grid lines on XY plots, independent of the major grid color.<br>&nbsp;</li>

	<li>For 3D wireframe plots, if both <i>Borders</i> and <i>Grid</i> are unchecked under <i>Draw</i> on the &quot;Contour Options&quot;
		dialog, then element borders will be drawn. In previous versions the default was grid lines, but those lines
		are often too sparse to give the surface much definition. If you are plotting more than a several hundred thousand
		points, though, this new behavior might result in a plot that is mostly black (or whatever the border color is). In
		that case be sure to check <i>Grid</i> and uncheck <i>Borders</i> on the Contour Options dialog.<br>&nbsp;</li>

	<li>Bug fix: DPlot did a poor job of handling CSV files with an abundance of blank entries, particularly if the
		last column in the first data line was blank. In many cases DPlot would get confused about which line the
		data started in, and/or might have reported that it could not find a pattern of data columns int the file.<br>&nbsp;</li>

	<li>Bug fix: The &quot;Label this point&quot; feature of <i>Edit Mode</i> for XY plots did not pick up the label
		unless the label text control was given the focus (and subsequently lost the focus, either by tabbing away
		or clicking on another control). The was generally a problem for the second and subsequent labels added with
		this feature, which set the default label to the previously-specified label text (so if you were happy with
		that default label, there was no reason to give the text control the focus).<br>&nbsp;</li>

	<li>Bug fix: The formatting buttons on the Legend dialog for XY plots did not always work on the first attempt,
		particularly when this dialog was opened by double-clicking on the legend.<br>&nbsp;</li>

	<li>Bug fix: The LAS well log file import plugin incorrectly interpreted files containing data lines exactly 256 characters
		long, or comment lines longer than 256 characters. There was also a roundoff error in determining the expected number of
		data lines for some combinations of START, STOP, and STEP values that might have led to an erroneous error message.<br>&nbsp;</li>

	<li>Bug fix: Axis labels/titles might have been drawn on the wrong side of a 3D view of 3D/4D data if negative scale
		factors on the X or Y axis were used.<br>&nbsp;</li>

	<li>Bug fix: <i>Date and Time</i> <a href="http://www.dplot.com/help/index.htm?helpid_numberformats.htm">number format</a>
		displayed pre-1900 dates as &quot;########&quot;, while <i>Calendar Date</i> format worked fine. The problem was
		due to DPlot originally being limited with dates in the same way that Excel is (Jan 1, 1900 through Dec 31, 2078).
		DPlot has for many years worked with dates from Oct 15, 1582 through Dec 31, 9999, but the text formatting for
		<i>Date and Time</i> number format was not updated to include this capability.<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

<item>
	<title>Improved output of Polynomial Curve Fit command</title>
	<link>http://www.dplot.com/revisions.htm#R2278</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2278"></a><h3>14 February, 2010<br>
	Version 2.2.7.8</h3>
	<ul>
	<li>Bug fix: Some user-specified tick mark intervals did not work especially well with calendar dates, in particular tick mark 
		intervals greater than 2 years and less than 10 resulted in a mess of early grid lines at a much smaller spacing, followed
		by a large gap.<br>&nbsp;</li>

	<li>The divisor in the <i>Standard error about the line</i> calculation that is one of the outputs of the
		<a href="http://www.dplot.com/help/index.htm?helpid_curvefit.htm">Polynomial Curve Fit</a> command has been 
		changed from <i>n-1</i> to <i>n-&lt;number of unknowns&gt;</i>. This value now matches the answer provided
		by Excel's LINEST function.<br>&nbsp;</li>

	<li>The trial version of DPlot now includes most of the file import and export plugin modules previously distributed
		only with the licensed version.<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

<item>
	<title>Enhancements to the Excel Add-In.</title>
	<link>http://www.dplot.com/revisions.htm#R2277</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2277"></a><h3>31 January, 2010<br>
	Version 2.2.7.7</h3>
	<ul>
	<li>Removed all dependencies on DPLOTLIB.DLL functions from the Excel Add-In: all communication with DPlot is now handled 
		entirely within the Add-In's VBA modules. This should result in fewer Excel security-related errors, and <b>may</b> mean 
		that the Add-In will work with the upcoming 64-bit version of Excel 2010... stay tuned.<br>&nbsp;</li>

	<li>For the Excel Add-In functions, added a hidden text notation with a description of the source data in the
		form &quot;Source: [Filename]Sheet!R1C1&quot;. This might be useful for recalling the source of the data in 
		a saved DPlot file. The note is initially placed at the upper left corner of the box surrounding a plot.
		No other consideration is given to the note placement, so if unhidden it might overlap other text entries
		(or other similar hidden notes). If you want to see this note (or move it to another location or 
		delete it), click the Note button on the toolbar.<br>&nbsp;</li>

	<li>Added $NC <a href="http://www.dplot.com/help/index.htm?helpid_text_shortcuts.htm">text shortcut</a>, which is 
		replaced by the 1-based curve index. This shortcut is only useful in the legend and in the 
		<a href="http://www.dplot.com/help/index.htm?helpid_operate_x.htm">Operate on X</a> and
		<a href="http://www.dplot.com/help/index.htm?helpid_operate_y.htm">Operate on Y</a> commands on the Edit menu.<br>&nbsp;</li>

    <li>Added the ability to specify a range in X to operate on with the 
		<a href="http://www.dplot.com/help/index.htm?helpid_removespikes.htm">Remove Random Spike</a> menu command.<br>&nbsp;</li>

	<li>Bug fix: Corrected a couple of problems with the <a href="http://www.dplot.com/features.htm#SRTM">SRTM file import plugin</a>.
		1) If &quot;Set X:Y scale factors to give proportional ground distances&quot; was checked (and this should have been
		labeled X:Y:Z scale factors) then the Z scale factor was not properly calculated, normally resulting in a greatly exaggerated
		Z scale in 3D views, and 2) The default tick mark interval was fouled up if the extents were greater than 20 minutes and
		less than or equal to 30 minutes.<br>&nbsp;</li>

	<li>Bug fix: <a href="http://www.dplot.com/help/index.htm?helpid_labelpoints.htm">Point labels</a> were misaligned 
		roughly 1/2 character to the left in enhanced metafiles.<br>&nbsp;</li>

	<li>Bug fix: The <a href="http://www.dplot.com/help/index.htm?integratecommand.htm">Integrate</a> macro/DDE command effectively
		ignored any previous SelectCurve command; the curve that was integrated may (or may not) have been that specified with 
		SelectCurve if more than 1 curve was present.<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

<item>
	<title>New macro commands, new features for selected text shortcuts.</title>
	<link>http://www.dplot.com/revisions.htm#R2276</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2276"></a><h3>6 December, 2009<br>
	Version 2.2.7.6</h3>
	<ul>
	<li>You can now abort a <i>Crop</i>, <i>Delete Points in Box</i>, or <i>Set Limits to Min/Max in Box</i> command 
		by pressing the Escape key before releasing the mouse button.<br>&nbsp;</li>

	<li>The macro <a href="http://www.dplot.com/help/index.htm?shellcommand.htm">Shell</a> command now correctly handles
		<i>command</i> parameters that include quotation marks (which might be needed for commands containing spaces).
		For example, in the following command the additional quotes are necessary because of the spaces in the filename
		plus the commandline parameter:<br>&nbsp;<br>

		<code>Shell(&quot;&quot;c:\Program Files\My Application\test.bat&quot; param1&quot;,1)</code>

		<br>&nbsp;<br>
		but would have resulted in the <i>command</i> being interpreted as a 0-length string in previous versions because 
		of the successive quotes.<br>&nbsp</li>

	<li>Most dialog boxes that expect numeric input will now accept equations (prefaced by an equals sign). These equations
		may include <a href="http://www.dplot.com/help/index.htm?helpid_text_shortcuts.htm">text placeholders</a>. For example
		on the <i>Reference Lines</i> dialog if you select <i>Y=</i> and &quot;=$MEAN(1)&quot; for the <i>At Value</i> entry,
		you will get a horizontal reference line at the mean Y value for the 1st curve.<br>&nbsp;<br>
		The principal difference between these text boxes and text boxes that accept character strings (titles, labels, etc.)
		is that the equation is evaluated immediately and is not preserved.<br>&nbsp;</li>

	<li>Added an option to the <a href="http://www.dplot.com/help/index.htm?helpid_fillregion.htm">Fill Between Curves</a>
		command on the Options menu to fill the area below a curve, only for those points less than or equal to some
		reference Y value.<br>&nbsp;</li>

	<li>The $YMIN, $YMAX, $ZMIN, and $ZMAX <a href="http://www.dplot.com/help/index.htm?helpid_text_shortcuts.htm">text 
		placeholders</a> may now include a range within which the min/max should be evaluated. For example $YMIN(2,1.6,2.4)
		is replaced by the minimum Y value of the 2nd curve between 1.6 <u>&lt;</u> X <u>&lt;</u> 2.4.<br>&nbsp;</li>

	<li>The <a href="http://www.dplot.com/help/index.htm?reflinecommand.htm">RefLine</a> macro/DDE command now
		accepts equations for all parameters. This is primarily useful for specifying the value, e.g.<br>&nbsp<br>
		<code>RefLine(1,1,0x00FF0000,30,=$YMAX(3),&quot;Max value, curve 3&quot;)</code>
		<br>&nbsp;</li>

	<li>Added code to correctly handle printing to PDF print drivers when the filename is specified using the
		<a href="http://www.dplot.com/help/index.htm?fileprintcommand.htm">FilePrint</a> command. (Before this release, some 
		print drivers produced a PostScript file in this case, others insisted on displaying the <i>Save As</i> dialog.) 
		DPlot now includes code to produce the expected results when using the Adobe PDF, PDF995, docuPrinter, or PDFcamp 
		drivers. (The Adobe PDF driver is distributed with Adobe Acrobat; the others are available from:<br>&nbsp;<br>
		<ul>
		<li>PDF995 from <a href="http://www.pdf995.com/" TARGET="_blank">Software995</a>.</li>
		<li>docuPrinter LT from <a href="http://www.neevia.com/" TARGET="_blank">Neevia Technology</a>.</li>
		<li>PDFcamp from <a href="http://www.verypdf.com/index.html" TARGET="_blank">veryPDF</a>.</li>
		</ul>
		<p>This change is mostly useful when batch-converting a large number of files when you do not want to continuously
		respond to the normal <i>Save As</i> dialog.
		<p><b>Please note:</b> No precautions have been added for other PDF print drivers. Results with drivers not mentioned 
		here will vary. If you have a pet PDF print driver that misbehaves with the FilePrint command and a specified filename
		(produces a PostScript file or insists on displaying the <i>Save As</i> dialog), 
		<a href="mailto:support&#64;dplot.com">let us know</a> and it is possible we'll add code to work around this 
		problem.<br>&nbsp;</li>

	<li>Added <a href="http://www.dplot.com/help/index.htm?request_function.htm">Request</a> macro function to retrieve a 
		dozen or so document-specific items from DPlot. The result of the Request function can then be used in subsequent 
		macro commands. For example, you can request &quot;ListPeaks&quot; and then use that output as the text of a 
		notation with the <a href="http://www.dplot.com/help/index.htm?textnotecommand.htm">TextNote</a>,
		<a href="http://www.dplot.com/help/index.htm?textnote3d_command.htm">TextNote3D</a> or 
		<a href="http://www.dplot.com/help/index.htm?textnoteexcommand.htm">TextNoteEx</a> commands.<br>&nbsp;</li>

	<li>Added several <a href="http://www.dplot.com/help/index.htm?helpid_exportdata.htm">request items</a> related to filenames 
		that you can retrieve from DPlot using a DPlot_Request call using DPLOTLIB.DLL or the new Request macro command: 
		filename, filetitle, fname, and path.<br>&nbsp;</li>

	<li>Bug fix: Ouch! The <i>mean</i> (and therefore the <i>standard deviation</i> report as well) shown by the <i>List Peaks</i>
		command was incorrect if a curve did not start at Y=0.<br>&nbsp;</li>

	<li>Bug fix: If the legend for a 2D bar chart was dragged outside the plot extents, the color blocks used in the legend 
		were clipped.<br>&nbsp;</li>

	<li>Bug fix: In 2D views of random 3D points with contour lines, if a triangle edge had two points exactly equal to the 
		contour value, no line was drawn.<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>


<item>
	<title>New features for Playback command.</title>
	<link>http://www.dplot.com/revisions.htm#R2275</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2275"></a><h3>18 November, 2009<br>
	Version 2.2.7.5</h3>
	<ul>
	<li>Added frame advance buttons to the <a href="http://www.dplot.com/help/index.htm?helpid_playback.htm">Playback</a> command.
		<br>&nbsp;</li>

	<li>For videos run with the Playback command, the filename, recording rate, first time, and zoom levels are now preserved from 
		one session to the next rather than using default values (no selected file, recording rate=playback rate, zoom=100%, and first
		time=0.)<br>&nbsp;</li>

	<li>Modified the Move/Copy Curves command on the Edit menu and the <span class="prog">corresponding 
		<a href="http://www.dplot.com/help/index.htm?movecurvescommand.htm">MoveCurves</a> macro/DDE command</span>. If 
		moving/copying to a new or empty document, the axis labels and scaling information (linear/log, number format, 
		extents, etc.) are copied to that document. In addition, and whether the target document is new/empty or not,
		curve colors are preserved.<br>&nbsp;</li>

	<li>The initial view (thumbnails, icons, details, etc.) in the Open/Save dialogs is now preserved for Windows XP and
		later versions. In addition (for Windows XP only), added options to specify the initial sort order using the 
		<a href="http://www.dplot.com/help/index.htm?helpid_genoptions.htm">General</a> command on the Options menu.
		(The reason for these settings is that the sort order can be <b>set</b> programmatically on XP, but seemingly 
		not <b>retrieved</b> from those dialogs. For Vista and later versions the sort order is preserved by the OS, so 
		these settings would be superfluous and are hidden and disabled.)<br>&nbsp;</li>

	<li>Streamlined the output of the <i>Number of Points</i> command on the <i>Info</i> menu. When all curves contain
		the same number of points, the output is now &quot;All &lt;M&gt; curves contain &lt;N&gt; points.&quot;, rather
		than listing each curve separately.<br>&nbsp;</li>

	<li>Bug fix: DPlot might have crashed with an integer overflow error when using custom contour levels that were very
		small relative to the total range in contour levels.<br>&nbsp;</li>

	<li>Bug fix: Small non-zero custom contour levels might have been shown as 0 in the legend and/or in contour line labels.
		<br>&nbsp;</li>

	<li>Bug fix: Background color for point labels with 3D/4D data sets was not saved to DPlot files.<br>&nbsp;</li>

	<li>Bug fix: Window menu on 3D scatter plots was fouled up and did not include the list of open documents (that list
		was erroneously shown at the bottom of the View menu). In addition, the &quot;Displayed values&quot; entry in 
		the status bar did not work correctly for scatter plots.<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

<item>
	<title>New features in Moving Average function; much-improved handling of bitmap images (BMP, GIF, JPG, etc.)</title>
	<link>http://www.dplot.com/revisions.htm#R2273</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2273"></a><h3>6 November, 2009<br>
	Version 2.2.7.3</h3>
	<ul>
	<li>Licensed version only: In addition to the prior moving average previously performed, the Moving Average plugin can
		produce a central or cumulative moving average. The plugin also gives the option (for prior and central averages)
		to produce (or not) averages at the tails (first N-1 points for a prior moving average, first and last (N-1)/2
		points for a central average). For more information see the associated 
		<a href="http://www.dplot.com/blog/2009/11/moving-average.html">blog entry</a>.<br>&nbsp;</li>

	<li>DPlot uses a different Windows routine to save bitmap images, with the result that you'll be able to save
		much larger images and experience fewer memory-related problems when working with multiple documents. For the 
		nuts-and-bolts explanation: DPlot previously created bitmaps with calls to CreateCompatibleBitmap, which unbeknownst
		to the red-faced author uses your video card's memory. (Some device drivers may be smart enough to fall back to 
		system memory if insufficient video memory is available, but most do not.) When saving large bitmap images you 
		might have encountered &quot;Insufficient memory for &lt;width&gt;w x &lt;height&gt;h bitmap.&quot; or a similar 
		message	for cropped images. In addition you might have run into problems when working with many documents, depending
		on how much available memory your video card has. DPlot now uses CreateDIBSection to create most bitmaps, which 
		uses user mode memory. Redrawing may take a few milliseconds longer now, but bitmaps are only limited by your
		physical RAM and/or page file size, up to 2Gb.<br>&nbsp;</li>

	<li>Bug fix: An uninitialized data problem might have led to &quot;Syntax error in function&quot; messages for the
		<a href="http://www.dplot.com/help/index.htm?helpid_f_of_x.htm">Y=f(X)</a> and similar commands with perfectly 
		valid functions.<br>&nbsp;</li>

	<li><span class="blue">Bug fix: One more goof in the 
		<a href="http://www.dplot.com/help/index.htm?manualscalecommand.htm">ManualScale</a> command introduced with 
		version 2.2.6.9 has been fixed. If you omitted either Y parameter, what <b>should</b> happen is DPlot uses
		the existing Y extent. But instead you might have received an error message concerning the Y extents being equal, 
		or worse, completely nonsensical Y extents.</span><br>&nbsp;</li>

	</ul>
	]]> 
	</content:encoded>
	</description>
</item>


<item>
	<title>Improved contour labels, new polar plot and probability scale options</title>
	<link>http://www.dplot.com/revisions.htm#R2270</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2270"></a><h3>1 November, 2009<br>
	Version 2.2.7.0</h3>
	<ul>
	<li>The function parser will now accept the FORTRAN ** operator for exponentiation. Also added checks to ensure
		that you <b>meant</b> to use the <a href="http://www.dplot.com/help/index.htm?helpid_f_of_x.htm">Y=f(X)</a> command 
		rather than <a href="http://www.dplot.com/help/index.htm?helpid_funcy.htm">Y=f(X,Y1,Y2,...)</a>.<br>&nbsp;</li>

	<li>DPlot does a somewhat better job of centering contour line labels on the respective contour. Also, for output to other
		than metafiles, for opaque line labels DPlot gives a bit more white space at the beginning and end of the label, and
		less white space (which previously tended to overwrite other lines unnecessarily) at the top and bottom of the label.<br>&nbsp;</li>

	<li>Changed the physical length of the pattern used for patterned line styles, taking the line width into account. In 
		previous versions the spaces between dashes and dots tended to close up with lines wider than about 0.04". If any line 
		styles on an XY plot are non-solid, the largest line width is used to determine the pattern length for <b>all</b>
		patterned line styles.<br>&nbsp;</li>

	<li>Licensed version only: &quot;More Curve Fits&quot; plugin now includes the equation form y=A+B*exp((C*x)^D). Depending
		on your input, this form may take several hundred iterations to converge to the best solution.<br>&nbsp;</li>

	<li>Probability scales are now clipped at 1.E-5% and 99.99999%. Previous versions were limited to 0.001 - 99.999%.<br>&nbsp;</li>

	<li>Added an option for polar plots to display angles as 0 to <u>+</u>180 degrees (or <u>+</u>&pi;, depending on number-formatting
		options) rather than the default 0 to 360 degrees.<br>&nbsp;</li>

	<li>Bug fix: The new version 2.2.6.9 $Y text shortcut did not work correctly.<br>&nbsp;</li>

	<li>Bug fix: Starting with version 2.2.6.6, DPlot botched up the legend for XY plots if you set the &quot;Maximum 
		number of rows&quot; entry to 1.<br>&nbsp;</li>

	<li>Bug fix: The <a href="http://www.dplot.com/exceladdin.htm">Excel Add-In's</a> XYZSurface and XYZScatter functions choked if 
		the Excel selection had one or more leading blank rows.<br>&nbsp;</li>

	<li>Bug fix: Reference lines on 1D plots ignored the line width setting if antialiasing was turned on.<br>&nbsp;</li>

	<li><span class="blue">Bug fix: Version 2.2.6.9's change allowing equations as parameters in macro/DDE commands broke the 
		<a href="http://www.dplot.com/help/index.htm?manualscalecommand.htm">ManualScale</a> command for 3D views of 3D/4D data.
		</span><br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

<item>
	<title>New triangle plot options and text placeholders for various plot parameters</title>
	<link>http://www.dplot.com/revisions.htm#R2269</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2269"></a><h3>17 October, 2009<br>
	Version 2.2.6.9</h3>
	<ul>
	<li>Added <i>$X(i,j)</i> and <i>$Y(i,j)</i> <a href="http://www.dplot.com/help/index.htm?helpid_text_shortcuts.htm">text placeholders</a>.
		When used, these placeholders are replaced by the <i>j'th</i> X or Y value of the <i>i'th</i> curve of an XY plot.<br>&nbsp;</li>

	<li><span class="blue">Many of the macro/DDE commands that accept numeric parameters will now accept equations, preceded by an equals sign.
		For example, in the command:
		<br>&nbsp;<br><code>
		[ManualScale(0,0,=CEIL($XMAX/100)*100,=CEIL($YMAX/10)*10)]
		</code>
		<br>&nbsp;<br>the high X value is set to the smallest multiple of 100 that is greater than or equal to the maximum X value. Similarly, the high Y value
		is set to the smallest multiple of 10 that is greater than or equal to the maximum Y value.</span><br>&nbsp;</li>

	<li>For triangle plots, added an option for X+Y+Z=1. If checked then the range along each axis is 0-1. (In previous versions X+Y+Z=100, with
		a range along each axis of 0-100.)<br>&nbsp;</li>

	<li>Added a <i>Hide</i> command to the right-click menu for curves in an XY plot. Previously this functionality was
		only available within the legend of a plot. Curves hidden with this option may be made visible with the
		<i>Hide Curves</i> or <i>Unhide All Curves</i> commands on the View menu.<br>&nbsp;</li>

	<li>Changed the behavior of 3D scale factors. Whether set with the <a href="http://www.dplot.com/help/index.htm?helpid_contourplot.htm">Contour Options</a>
		or <a href="http://www.dplot.com/help/index.htm?contouroptionsoptionsmenu1.htm">Scatter Plot Options</a> dialogs, with a 
		<a href="http://www.dplot.com/help/index.htm?contourscalescommand.htm">ContourScales</a> macro/DDE command, or read from a DPlot file,
		if any scale factor is set to 0 then it will be reset to the value normally determined by the &quot;Always auto-adjust scale factors on 3D plots&quot;
		option of the <a href="http://www.dplot.com/help/index.htm?helpid_genoptions.htm">General</a> command on the Options menu, or forced to 1.0
		if that option is not selected. This is primarily of use to programmers who want a fixed, known relationship between the physical distances 
		along the X and Y axes, but who don't necessarily know the Z extents (at least not without a bit of extra work).<br>&nbsp;</li>

	<li>Changed the behavior of &quot;Specify extents&quot; vs. zooming. In this release if the &quot;Specify extents&quot;
		box is checked when you click OK on the <a href="http://www.dplot.com/help/index.htm?manualscalecommand.htm">Extents/Intervals/Size</a>
		dialog box, all previous zooms are deleted. In previous versions zoom information was maintained, and that
		information was written to saved DPlot files. The trouble with doing that is there is not sufficient information
		in the DPlot file to tell which operation took place last, and DPlot always processed the zoom extents and 
		used those even though you might have subsequently used &quot;Specify extents&quot;.<br>&nbsp;</li>

	<li>Eliminated an annoyance. In previous versions if you had a mouse-activated 
		<a href="http://www.dplot.com/help/index.htm?helpid_labelpoints.htm">point label</a> <b>and</b> the
		&quot;Show coordinates in popup window when mouse hovers over a data point&quot;
		<a href="http://www.dplot.com/help/index.htm?helpid_genoptions.htm">General</a> option was checked,
		when hovering over a point you'd sometimes get the mouse-activated label, which 1/2 second later would
		disappear and be replaced with the popup window displaying the point coordinates. In this release
		that popup window will not be displayed if a mouse-activated point label is currently being
		displayed.<br>&nbsp;</li>

	<li>Added two new inverted triangle <a href="http://www.dplot.com/help/index.htm?symboltypecommand.htm">symbol types</a> 
		(28 and 284) that line up vertically with the non-inverted types 7 and 263. (As with symbols 7 and 263, symbol types 
		9 and 265 are placed such that the geometric center of the triangle is at the data point.)<br>&nbsp;</li>

	<li>When pasting 3 or 4 columns of data from the clipboard into a 3D/4D surface plot or scatter plot, DPlot will now accept dates
		and times. Previous versions were restricted to numbers.<br>&nbsp;</li>

	<li>Bug fix: The feature of showing a popup window displaying a data point's coordinates for randomly-spaced 3D data has
		always been broken unless the X and Y extents were relatively small. (The test performed for distance from a data point
		was in data space rather than pixels.)<br>&nbsp;</li>

	<li>Bug fix: Shadows for button-activated text notations were not drawn correctly on Vista systems. Those shadows are no
		longer drawn on Vista.<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

<item>
	<title>New triangle plot options. Several bug fixes</title>
	<link>http://www.dplot.com/revisions.htm#R2268</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2268"></a><h3>4 October, 2009<br>
	Version 2.2.6.8</h3>
	<ul>
	<li>In previous versions the ability to <a href="http://www.dplot.com/help/index.htm?how_pan.htm">pan a 2D plot</a>
		left/right/up/down using the keyboard arrow keys or by dragging the mouse was limited to plots that you had 
		zoomed in on. This release removes that restriction. Also, panning with the mouse is now supported by DPlot Jr
		and DPlot Viewer, and for the full version and DPlot Jr panning with either the arrow keys or the mouse creates 
		an Undo file.<br>&nbsp;</li>

	<li>Added Ab-An-Or (Albite, Anorthite, Orthoclase) layout to <a href="http://www.dplot.com/triangle_plot.htm#ABANOR">triangle plots.</a>
		<br>&nbsp;</li>

	<li>Added an &quot;Invert&quot; button to the <i>Hide Curves</i> dialog, which toggles the visibility of all curves.<br>&nbsp;</li>

	<li>Bug fix: Undo files saved the checkbox options on the <i>General Options</i> dialog, but no other entries. So there was no way, 
		for example, to &quot;undo&quot; changing the default decimal symbol or the maximum number of data points for which antialiasing
		would be applied.<br>&nbsp;</li>

	<li>Bug fix: 3D bar charts ignored the &quot;Custom levels&quot; contour setting, other than the low and high values. Other levels
		were distributed evenly between the low and high.<br>&nbsp;</li>

	<li>Bug fix: When pasting data from the Clipboard, completely blank columns were added as new curves with 0 points. This might have led to,
		at best, confusing subsequent operations. In this version after pasting Clipboard data DPlot checks for and eliminates new curves with
		0 points.<br>&nbsp;</li>

	<li>Bug fix: The <a href="http://www.dplot.com/help/index.htm?helpid_reflines.htm">Reference Lines</a> dialog 
		might have rounded off the reference X/Y value simply by opening the dialog and clicking OK. This was particularly 
		a problem with calendar dates and times where the reference value included fractional seconds, but the time 
		formatting string used on the corresponding axis did not.<br>&nbsp;</li>

	<li>Bug fix: Starting with version 2.2.6.6, 1D DPlot files with &quot;Specify extents&quot; checked did not properly save those extents. 
		Subsequent attempts to open those files usually resulted in DPlot crashing. For these files saved with versions 2.2.6.6 or 2.2.6.7,
		DPlot will now turn off &quot;Specify extents&quot; and otherwise process the file properly. If you then re-enter those extents and 
		re-save the file, all will be well.<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

<item>
	<title>Several bug fixes, improved zooming with mouse</title>
	<link>http://www.dplot.com/revisions.htm#R2267</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2267"></a><h3>12 September, 2009<br>
	Version 2.2.6.7</h3>
	<ul>
	<li>Changed the behavior of zooming out with the mouse wheel. In previous versions using the mouse wheel zoomed out by a factor of 2. In
		this version zooming out with the mouse wheel is equivalent to clicking the &quot;Zoom out&quot; button on the toolbar, which will
		restore the previous zoom extents. (The 2x factor in previous versions was only approximate. DPlot would adjust the plot extents to
		give &quot;nice&quot; tick mark intervals. In many cases zooming in, then zooming out with the mouse wheel resulted in different 
		extents than you started with.)<br>&nbsp;</li>

	<li>Bug fix: If the date format for calendar dates (set with the 
		<a href="http://www.dplot.com/help/index.htm?helpid_numberformats.htm">Number Format</a> menu command) did not match the
		&quot;Assume input dates are of the form d/m/y&quot; setting under Options&gt;General, DPlot fouled up dates in text boxes.
		This was especially evident on the <a href="http://www.dplot.com/help/index.htm?manualscalecommand.htm">Extents/Intervals/Size</a>
		dialog box: on entry dates would be displayed using the selected date format, but upon clicking OK were interpreted using the
		Options&gt;General setting. So the month and day might have been transposed even though the dates had not been edited in any
		way.<br>&nbsp;</li>

	<li>Bug fix: For 3D views of random 3D points, symbols drawn at data points might have been drawn when they should have been hidden by other
		parts of the surface. This problem sometimes occurred when symbols overlapped each other.<br>&nbsp;</li>

	<li>Bug fix: Zooming in with the mouse wheel or with CTRL+&lt;number&gt; did not work properly if the lower extent was a negative number. In
		that case the new low extent would generally be 0 or close to it, regardless of the previous value.<br>&nbsp;</li>

	<li>Bug fix: If you used the &quot;Zoom out&quot; button on the toolbar to zoom all the way out, DPlot no longer received mouse wheel
		messages until you performed some action that restored the focus to the main window.<br>&nbsp;</li>

	<li>Bug fix: Recent &quot;fix&quot; to the &quot;Delete Points in Box&quot; command did not work with monotonically increasing X
		values if the left side of the box was positioned before the start of the data.<br>&nbsp;</li>

	<li>Bug fix: Ugh. Starting with version 2.2.6.5, Generate menu plugins distributed with DPlot that resulted in a dialog box being 
		displayed were amended such that the description included a trailing ellipsis, to make those menu commands adhere to Windows
		guidelines. Unfortunately this broke the <a href="http://www.dplot.com/help/index.htm?runplugincommand.htm">RunPlugin</a>
		macro/DDE command, unless the &quot;Plugin Description&quot; argument included that trailing ellipsis.<br>&nbsp;</li>

	<li>Bug fix: Amended a fix in <a href="http://www.dplot.com/old_revisions.htm#R2167">Version 2.1.6.7</a> for very long line segments 
		on XY plots (made very long by zooming in or setting the plot extents to a small fraction of the data extents). In some cases those
		line segments might have had an incorrect slope because the scaled endpoint coordinates were truncated to fit in a 2-byte integer.
		This release handles those line segments better on XP and Vista systems.<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

<item>
	<title>Several improvements for developers, plus a few minor bug fixes</title>
	<link>http://www.dplot.com/revisions.htm#R2266</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2266"></a><h3>6 September, 2009<br>
	Version 2.2.6.6</h3>
	<ul>
	<li>Improved the efficiency of the &quot;Delete Points in Box&quot; command on the Edit menu. The improvement will especially be noticeable
		for large (&gt; 100K points or so) data sets. If a plot contains any 
		<a href="http://www.dplot.com/help/index.htm?helpid_labelpoints.htm">point labels</a> DPlot will continue to use the previous, slower
		routine.<br>&nbsp;</li>

	<li>Amended <a href="http://www.dplot.com/help/index.htm?legendcommand.htm">Legend</a> macro/DDE command to accept a 
		$LEGEND(<i>n</i>) placeholder, which will be replaced with the legend for curve <i>n</i>. This might be useful when operating on
		an existing curve in some way, then appending a description of the operation to the legend of the source curve.<br>&nbsp;</li>

	<li>For polar plots, if the start point of a line segment has a radius less than the low value specified with 
		<a href="http://www.dplot.com/help/index.htm?manualscalecommand.htm">Extents/Intervals/Size</a> then that endpoint is now
		drawn at the center of the plot. In previous versions that line segment would not be drawn.<br>&nbsp;</li>

	<li>For developer's of <a href="http://www.dplot.com/help/index.htm?helpid_plugin.htm">Generate</a> plugins, amended the Generate menu based on 
		subfolders below the \plugins\generate folder. If plugins are found below that folder, DPlot will add a sub-menu with the folder name, and those
		plugins will be added to that sub-menu rather than the Generate menu. If you write a plugin you believe would be useful to others, please 
		<a href="mailto:support&#64;dplot.com">let me know</a>. Credit will of course be given where it is due (or not: it is up to you).<br>&nbsp;</li>

	<li>Removed the limitation on the number of files processed by a <a href="http://www.dplot.com/help/index.htm?forfilesincommand.htm">ForFilesIn</a>
		macro loop. Previously there was a limit of 256 files.<br>&nbsp;</li>

	<li><span class="blue">Added the function <a href="http://www.dplot.com/lib/index.htm?dplot_alwaysactivate.htm">DPlot_AlwaysActivate</a> 
		to DPLOTLIB.DLL. Normally, calls to DPlot_Command, DPlot_Plot, etc. cause DPLOT.EXE to be activated. Use <b>DPlot_AlwaysActivate(0)</b> if 
		your application produces plots without user interaction and it is inconvenient and/or annoying for DPlot to be activated with each 
		new plot. This command has no effect if DPlot is hidden.</span><br>&nbsp;</li>

	<li>Bug fix: In the <a href="http://www.dplot.com/help/index.htm?helpid_f_of_x.htm">Y=f(X)</a> and similar functions, in some cases
		DPlot would add an additional point due to a precision limitation. For example if the <i>From X</i> value was 0, the <i>To X</i>
		value was 0.049999, and the interval was 1.E-6, DPlot would find that 49999 intervals starting at 0 was equal to, roughly,
		0.049999 - 6.9E-18: less than 0.049999, so a point was added. This version takes into account the inherent error in double precision
		numbers and (in this case) produces 50K points from 0 to 0.049999.<br>&nbsp;</li>

	<li>Bug fix: A small precision error in comparing data extents to extents specified with the 
		<a href="http://www.dplot.com/help/index.htm?manualscalecommand.htm">Extents/Intervals/Size</a> command with 3D views 
		of random 3D/4D points might have resulted in triangles being omitted that should have been drawn.<br>&nbsp;</li>

	<li>Bug fix: In some cases if the number of legend entries was equal to some multiple of the &quot;Maximum number of rows&quot; entry
		for XY plots, you would get an additional unwanted column (all white space) in the legend.<br>&nbsp;</li>

	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

<item>
	<title>Several bug fixes</title>
	<link>http://www.dplot.com/revisions.htm#R2265</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2265"></a><h3>13 August, 2009<br>
	Version 2.2.6.5</h3>
	<ul>
	<li>Corrected a few mostly cosmetic problems with menu commands for &quot;Generate&quot; plugins. Ellipses were not shown for commands
		that caused a dialog box to be displayed. Generate plugin menu commands were not disabled if a plot was not open.<br>&nbsp;</li>

	<li>Bug fix: The &quot;Delete Points in Box&quot; command on the Edit menu stopped short; it would not delete the last point in any 
		curve.<br>&nbsp;</li>

	<li>Bug fix: It was possible to crash DPlot by using the mouse wheel to zoom out to exceptionally large numbers (&gt; ~2.E+308 on a linear scale,
		difference in logarithms of the extents greater than 308 on a logarithmic scale.)<br>&nbsp;</li>

	<li>Bug fix: When zooming in with the mouse wheel, roundoff error forced the extents on a logarithmic X axis to be 2 and sometimes 3 log cycles.
		<br>&nbsp;</li>

	<li>Bug fix: Several dialog boxes (in particular but not limited to <a href="http://www.dplot.com/help/index.htm?helpid_f_of_x.htm">Y=f(X)</a>)
		that displayed a list of unit choices for increment in X, generally tied to the number format used for the X axis, might have crashed on 
		entry with an integer overflow error. This was especially true with calendar dates. The problem occurred when attempting to figure out the 
		best units to use for the X axis; for calendar dates, for example, DPlot checked to see whether the existing curves had a spacing between
		points close to 1 year, month, day, hour, minute, second, or millisecond. If the check made it all the way down to milliseconds with a 
		modern date then the test was very prone to crashing with an integer overflow error (a date in days multiplied by 8.64x10<sup>7</sup>
		milliseconds per day is generally a bit large for 4 byte integers). Thanks to john_in_sandiego for pointing out the problem.
		<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>


<item>
	<title>Several bug fixes, improvements to Garmin and SRTM file imports.</title>
	<link>http://www.dplot.com/revisions.htm#R2264</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2264"></a><h3>28 July, 2009<br>
	Version 2.2.6.4</h3>
	<ul>
	<li>(Licensed version only) Modified Garmin GPX file import plugin to work with GPX files whose records do <b>not</b> contain a &lt;time&gt; field. In this case, 
		of course, you cannot plot speed, or plot altitude vs. elapsed time or date/time.<br>&nbsp;</li>

	<li>At request, slightly modified the popup window that appears when hovering over a data point on an XY plot. If multiple independent axes are used <b>and</b>
		the curve containing the point is associated with the 2<sup>nd</sup> Y axis, the Y value is presented as &quot;Y2=&lt;value&gt;&quot;.<br>&nbsp;</li>

	<li>Bug fix: It was possible to cause DPlot to crash when zooming on a logarithmic scale if you simply clicked and released the mouse button (rather than dragging
		out a rectangle). What <b>should</b> happen in this case is that the plot is zoomed in by a factor of 2, centered on the cursor position but
		forced to be within the current plot extents. If you clicked near a plot edge that last operation might have resulted in a negative value for an extent, leading
		to an illegal math operation and crash.<br>&nbsp;</li>

	<li>Bug fix (Licensed version only): <a href="http://www.dplot.com/features.htm#SRTM">SRTM</a> plugin did not properly handle 3-second files (that is, all areas other
		than the United States) for which you did not plot the entire 1&deg; x 1&deg; extents of the file.<br>&nbsp;</li>

	<li>Bug fix: When reading text files if you selected &quot;Alternating X,Y columns&quot; but only a single X,Y pair, the Y axis label was erroneously set to the
		column heading for the matching X column (X and Y axis labels were identical, in other words).<br>&nbsp;</li>

	<li>Bug fix: List boxes displaying lists of curves/groups were drawn with all lines from the corresponding legend entry or axis title if that text contained line
		breaks. The result was an overlapping mess of text. In this version only the first line is used in those list boxes.<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

<item>
	<title>Several bug fixes, many related to surface plots. Improved (though still beta) OverlayDocument command.</title>
	<link>http://www.dplot.com/revisions.htm#R2263</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2263"></a><h3>17 July, 2009<br>
	Version 2.2.6.3</h3>
	<ul>
	<li>DPlot does a better job of handling multiple-monitor setups at startup. In previous versions DPlot <b>always</b>
		appeared on the primary monitor.<br>&nbsp;</li>

	<li>Made several minor improvements to <a href="http://www.dplot.com/features.htm#SRTM">SRTM file import plugin</a>:
		1) Added an option to correct X & Y scale factors such that distances along each axis are equivalent. 2) Added
		code to set the default tick mark interval to more aesthetically pleasing units on the X and Y axes: 1, 2, or 3 minutes
		depending on the extents of the plot.<br>&nbsp;</li>

	<li>Bug fix: Corrected a roundoff problem that often caused the omission of labels along the axes
		of surface plots at one or both ends, particularly for &quot;Degrees, Minutes&quot; or 
		&quot;Degrees, Minutes, Seconds&quot; 
		<a href="http://www.dplot.com/help/index.htm?helpid_numberformats.htm">number formatting.</a><br>&nbsp;</li>

	<li>Bug fix: Recent improvements with saving image files had a side effect of fouling up prints of 2D and 3D views of
		surface plots with shaded color bands and XY plots that included partially transparent symbols. (Both of these plot 
		types are drawn to printer-compatible bitmaps, then the bitmap is printed.) In general fonts were larger (in some 
		cases much larger) than they should have been.<br>&nbsp;</li>

	<li><span class="blue">Bug fix: The |TITLE<i>n</i>| replaceable parameters for the 
		<a href="http://www.dplot.com/help/index.htm?filesaveascommand.htm">FileSaveAs</a> command have been broken in the 
		last several releases, sometimes resulting in a &quot;NULL result for replaceable parameter...&quot; error message.
		</span><br>&nbsp;</li>

	<li>Bug fix: When using shaded bands for a surface plot, roundoff error might have incorrectly forced the
		last legend entry to be written in the next column, so that you'd have one extra legend entry in its
		own column when there was clearly room for that entry in the previous column. Depending on plot 
		size this might have resulted in that legend entry being clipped.<br>&nbsp;</li>

	<li>Improved on the still-mostly-undocumented feature of overlaying one document with another. The only way to 
		access this feature at the moment is with the <a href="http://www.dplot.com/help/index.htm?overlaydocument_command.htm">OverlayDocument</a>
		macro/DDE command. For more	information and an example see the related <a href="http://dplot.com/blog/2009/07/plot-overlays.html">blog</a>
		entry.<br>&nbsp;</li>
	</ul> 
	]]> 
	</content:encoded>
	</description>
</item>


<item>
	<title>JPEG quality setting, improved curve fitting, several bug fixes</title>
	<link>http://www.dplot.com/revisions.htm#R2261</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2261"></a><h3>17 June, 2009<br>
	Version 2.2.6.1</h3>
	<ul>
	<li>By popular demand, added a quality setting for JPEG export. You will most likely find that the 4<sup>th</sup>
		of the 5 settings (&quot;qood&quot;, the previous default) is the minimum acceptable quality. The
		5<sup>th</sup> setting is lossless and so won't produce the artifacts common to JPEG files, but the
		file size is much larger.<br>&nbsp;</li>

	<li>(Licensed version only). Improved initial guesses for the equation form Y=A(X+B)^C. Previous versions 
		tended to blow up with data that had a negative slope. Also added the ability to specify the extents
		of the curve generated by the fit equation.<br>&nbsp;</li>

	<li><span class="blue">Modified the Excel Add-In commands XYZSurface and XYZScatter to skip over blank cells:
		if any of the X,Y, or Z cells are empty, no point is added. Also added better error messages for finding
		bad numbers, rather than relying on Excel's generic &quot;Type mismatch&quot; errors.</span><br>&nbsp;</li>

	<li>Bug fix: Zooming out with the mouse wheel might have caused DPlot to crash with a logarithmic scale.<br>&nbsp;</li>

	<li>Bug fix: Fixed a few issues with writing %APPDATA%/DPlot/dplot.ini. In previous versions the file might
		have become mangled up by the macro editor.<br>&nbsp;</li>

	</ul>
	]]> 
	</content:encoded>
	</description>
</item>


<item>
	<title>Correction to new IUGS ultramafic rock feature for ternary plots; minor change to List Peaks feature.</title>
	<link>http://www.dplot.com/revisions.htm#R2260</link>
	<description>
	<content:encoded>
	<![CDATA[
	<a name="R2260"></a><h3>2 June, 2009<br>
	Version 2.2.6.0</h3>
	<p>Very minor changes this time. Mailing list updates will not be sent. If you're a licensed user, you can
	get this update at the same link you received in the last update message, or with &quot;Check for Updates&quot;
	on the Help menu.</p>

	<ul>
	<li>Fixed the boundary between peridotites and pyroxenites on the new IUGS ultramafic rock classification
		scale for <a href="triangle_plot.htm">triangle plots</a>, and made a few changes to the label placement
		on the mafic rock plot to give a bit more room for the Y and Z axis labels.<br>&nbsp;</li>

	<li>Bug fix: Fixed a couple of minor problems with the List Peaks dialog. In particular for 3D/4D data you'd 
		get semi-random	characters in the output if you unchecked all options.<br>&nbsp;</li>
	</ul>
	]]> 
	</content:encoded>
	</description>
</item>

</channel>
  
</rss>
