[Nplot-devel] [ nplot-Bugs-2669326 ] DateTimeAxis throws unhandled exception due to WorldMax Bug.

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

Bugs item #2669326, was opened at 2009-03-06 20:07
Message generated for change (Comment added) made by nobody
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=821568&aid=2669326&group_id=161868

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General
Group: 0.9.10.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: DateTimeAxis throws unhandled exception due to WorldMax Bug.

Initial Comment:
In the file attached, I am trying to create two linePlots and add them to a single Plotting Surface, based off NPlot's example code. 
If the second LinePlot is not added to the plotting surface, everything works.

However, if the second line is added (using the same date range) the program crashed with a "ArguementOutOfRangeException: The added or subtracted value results in an un-representable DateTime.
Parameter name: months" on DateTimeAxis.cs line 587.

The real problem seems to be traced back to lines 326 and 327 of the file:
		DateTime worldMinDate = new DateTime( (long)this.WorldMin );
		DateTime worldMaxDate = new DateTime( (long)this.WorldMax );

The WorldMin seems to be 0, the "dawn of time", so to speak, and the WorldMax is some ungodly large number. (And I'm only trying to chart 50 days worth of data, and its larger than 50 days in ticks). That's as far as I've narrowed it so far. A breakpoint where the property is set might help narrow it done, and I'm going to try that next.

Thanks for all the great work you've done so far. Good Hunting.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-03-19 21:58

Message:
I've seen the same exception before.  I was using a TradingDateTimeAxis for
a CandlePlot but was setting the axis before adding the plot.  This caused
the WorldMin to remain zero causing the worldMinDate to be invalid.  I
worked around this problem by setting the CandlePlot data first, and then
creating a new TradingDateTimeAxis initialized from the CandlePlot's
SuggestXAxis() call before passing it into the graph.  Then when I stepped
through the NPlot source, WorldMin was no longer zero and the worldMinDate
was correct.

----------------------------------------------------------------------

Comment By: Nobody/Anonymous (nobody)
Date: 2009-03-09 13:54

Message:
The email address for follow up on this ticket is redrobot AT gmail.com.
Once again, thanks for all the great work you've done so far.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=821568&aid=2669326&group_id=161868