With 2.0.47, I was working on a plot and used the Info>Distance from command. With the input dialog box up, I tried to type the date and time into X1. As soon as I typed "2/" for the date, DPlot "disappeared", ie, crashed and blew up with no error message or complaint.
Seems to work fine with mouse input. It just didn't like the slash character when I started typing the date.
Distance From Command
Moderator: DPlotAdmin
- DPlotAdmin
- Posts: 2312
- Joined: Tue Jun 24, 2003 9:34 pm
- Location: Vicksburg, Mississippi
- Contact:
Well that's certainly rude, isn't it? Thanks for pointing out the problem, will fix this as soon as possible.
Visualize Your Data
support@dplot.com
support@dplot.com
- DPlotAdmin
- Posts: 2312
- Joined: Tue Jun 24, 2003 9:34 pm
- Location: Vicksburg, Mississippi
- Contact:
Fixed. You can get the fixed version using Help>Check for Updates.
There were two separate problems here:
1) Updating the display every time a text box changed (as in typing a single key), as opposed to waiting until the text box lost focus. I can't think of a good reason for doing this and am not sure why it was written that way to start with, other than I was just having a bad day. Dates are an obvious problem, but any sort of multi-digit entry would normally result in nonsense initial answers. In the case of dates, DPlot saw your "2/", knew it wasn't a valid date, so tried to evaluate it as an equation. And that led to the second, worse problem:
2) The function parser crashed if an operator was not followed by an operand. I'm surprised this one hasn't been caught before, as it has been there from the start. In any case it is now fixed. "2/" as an equation now results in an error message.
Thanks for pointing out the problem(s).
There were two separate problems here:
1) Updating the display every time a text box changed (as in typing a single key), as opposed to waiting until the text box lost focus. I can't think of a good reason for doing this and am not sure why it was written that way to start with, other than I was just having a bad day. Dates are an obvious problem, but any sort of multi-digit entry would normally result in nonsense initial answers. In the case of dates, DPlot saw your "2/", knew it wasn't a valid date, so tried to evaluate it as an equation. And that led to the second, worse problem:
2) The function parser crashed if an operator was not followed by an operand. I'm surprised this one hasn't been caught before, as it has been there from the start. In any case it is now fixed. "2/" as an equation now results in an error message.
Thanks for pointing out the problem(s).
Visualize Your Data
support@dplot.com
support@dplot.com
- DPlotAdmin
- Posts: 2312
- Joined: Tue Jun 24, 2003 9:34 pm
- Location: Vicksburg, Mississippi
- Contact:
Uh-oh. The "fix" to the function parser ended up invalidating many perfectly legal equations along with those it was trying to catch, like "Y=X/". Anybody who installed 2.0.4.8 using Help>Check for Updates prior to 11 Apr, 14:50 US CDT will need to do it again. Sorry for the inconvenience.
Visualize Your Data
support@dplot.com
support@dplot.com