octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #54551] poor auto axes limits chosen with 3-D


From: anonymous
Subject: [Octave-bug-tracker] [bug #54551] poor auto axes limits chosen with 3-D patches
Date: Wed, 22 Aug 2018 11:48:02 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.75 Safari/537.36

URL:
  <http://savannah.gnu.org/bugs/?54551>

                 Summary: poor auto axes limits chosen with 3-D patches
                 Project: GNU Octave
            Submitted by: None
            Submitted on: Wed 22 Aug 2018 03:47:58 PM UTC
                Category: Plotting
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Performance
                  Status: None
             Assigned to: None
         Originator Name: Andy Potvin
        Originator Email: address@hidden
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 4.4.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

Run the attached M-file to see Octave choose axes limits poorly.  I think the
bug has something to do with using 3-D patches.

Also, I attach my Octave command line output.  Note that I also get a weird
warning about "allowing norm to match units value normalized" - WTF is that?

Finally, you may recognize me as a former MathWorks developer.  I'm  running
into lots of bugs trying to make a (sudoku puzzle) GUI work in Octave.  It
works just fine in MATLAB.[FN1]  Anyway, I don't have a lot of time to chase 
down Octave bad behavior. [FN2]  If you put me in touch directly with the
developer of various ButtonDownFcn's, ButtonMotionFcn's and KeyPressFcn's I
can point the person to LOTS of bugs that I don't have time to reduce to a few
lines of code for a bug report.

Thanks and Best regards,
Andy Potvin
address@hidden
(626) 226-8436

[FN1] Truth be told, I've found and had to work around a few stupid MATLAB
bugs too.

[FN2] It took me MANY hours to produce the bug report here because I had to
reduce my multi-thousand-line GUI code to the two offending  line at the core
of the bug report.




    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Wed 22 Aug 2018 03:47:58 PM UTC  Name: ob_lim.m  Size: 483B   By: None

<http://savannah.gnu.org/bugs/download.php?file_id=44822>
-------------------------------------------------------
Date: Wed 22 Aug 2018 03:47:58 PM UTC  Name: ob_lim_report.txt  Size: 1KiB  
By: None

<http://savannah.gnu.org/bugs/download.php?file_id=44823>
-------------------------------------------------------
Date: Wed 22 Aug 2018 03:47:58 PM UTC  Name: ob_lim_command_output.txt  Size:
5KiB   By: None

<http://savannah.gnu.org/bugs/download.php?file_id=44824>

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?54551>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]