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

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

[Octave-bug-tracker] [bug #58956] Empty plot for certain xlim / ylim set


From: Hg200
Subject: [Octave-bug-tracker] [bug #58956] Empty plot for certain xlim / ylim settings
Date: Sat, 29 Aug 2020 04:00:22 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Fedora; Linux x86_64; rv:78.0) Gecko/20100101 Firefox/78.0

Follow-up Comment #9, bug #58956 (project octave):

Thank you for your feedback. Speaking of alternative bugfixes, I don't think
that just correcting the camera position is enough to solve the whole
problem.

If I undo the patch from bug #54551 and add 

++
set(gca, 'CameraPosition', [0.014392034052167, 0.134014656653948,
2.411976487699734]*1e13);
--

after "axis equals" in three_body_planar.m (see comment #8), the axis and
scatter objects are displayed correctly, but the trajectories (= line plots)
in the first figure, before the loop begins are still invisible. To see the
demo correctly, you may take a fresh copy of three_body_planar.m, without
modification and remove "axis equal" and uncomment the following lines:

++
dz = 1/sqrt((xrange(2)-xrange(1))^2+(yrange(2)-yrange(1))^2);
daspect ([1, 1, dz]);
--

Not showing the lines isn't a smoothing artifact, since

++
set (gcf, 'graphicssmoothing', 'off');
--

does not make the lines appear (references: bug #57336, bug #56979, bug
#54554).

I still have a doubt it's a problem when (far+near)/(far-near) in glOrtho gets
too big. Question: Is there a documentation on
"axes::properties::update_camera", or do we have to analyze the source code? I
want to understand the transformation matrices but it costs much time to go
through the code.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58956>

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




reply via email to

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