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

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

[Octave-bug-tracker] [bug #44503] 'set (gca, camera.......)' doesn't upd


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #44503] 'set (gca, camera.......)' doesn't update 3D plots
Date: Tue, 10 Mar 2015 20:57:54 +0000
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:33.0) Gecko/20100101 Firefox/33.0 SeaMonkey/2.30

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

                 Summary: 'set (gca, camera.......)' doesn't update 3D plots
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Tue 10 Mar 2015 09:57:53 PM CET
                Category: Plotting
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Any

    _______________________________________________________

Details:

Maybe I overlook something, but:

sombrero
get (gca, "cameraposition")
ans =

   -91.3142  -119.0030     6.3622

>> set (gca, "cameraposition", [-910, -420, -20])
>> drawnow
>>


doesn't update (rotate) the plot.
Only after I press the "rotate" button and click in the figure, the figure
suddenly rotates to the new camera position property.

=> Shouldn't it rotate immediately after the set() command, or after
"drawnow"?

Matlab (r2015a) does rotate a 3D plot (= adapts to new cameraposition)
immediately after the "set" command.

After the above actions, trying to rotate the plot by dragging with the mouse
doesn't work anymore. Apparently the "camerapositionmode" remains fixed to
"manual". 
That seems aother ML incompatibility; ML resets the camerapositionmode to
"auto" after clicking the "rotate" button and dragging a 3D figure corner. To
be honest, I'd expect user actions like clicking a button to override previous
system settings; OTOH maybe it is meant this way to prevent tampering with
plots?

I report the 2nd issue here as well as I suspect (gamble) the two are related.
If they're not I'll gladly open a new bug report.





    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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