On 10/10/2013 07:32 AM, Reza Housseini
wrote:
This is the right thing to do, but probably beyond what we can
implement just now.
Could do this, but I like the next option better.
Simple and safe. Probably the best we can do right now. I'll file
a bug report about it. And, for implementation, it isn't necessary
to give the warning if the axis scales are logarithmic since there
is plenty of room then.
I've purged the bug list of the "Crash" reports which weren't really
crashes. This still leaves 23 instances which I posted to the Bug
Fix List (http://wiki.octave.org/3.8_Bug_Fix_List). I've marked
them all as nice to fix, but not required to fix, before the next
release. If someone else would like to go through this smaller list
and identify items they feel really should be in the required
category that would be helpful. For bug #40121, I was the original
reporter and the case of using dbquit within a graphics callback is
obscure enough that I don't think too many people will run into it.
Hence, I don't deem it a must-fix bug before release.
--Rik
|