Re: help with pan, rotate3d, and zoom functions

[Michael Goffioul]

On Fri, Sep 12, 2014 at 3:32 PM, John W. Eaton <address@hidden> wrote

Assuming Octave's classdef support is sufficient, is there any objection to changing Octave's implementation to use a handle class object instead of the current simple string property?

There's one thing you must be aware of with the current classdef support and handle class: circular references are not handled properly. This can lead to memory leak if you use handle class objects that refer to each other.

Michael.

 

Is there an objection to making the pan function operate on figures instead of axes?  I think that's required for compatibility.

How is rotate3d supposed to work on either axes or figures?  Is the rotate3d object for an axis object actually just another reference to the rotate3d object of the parent figure?  It seems like that would be simple to do by storing the handle class object in the figure object that contains the axes object.  Is there any reason that zoom and pan should not allow axes arguments as well?

jwe