|
From: | Rik |
Subject: | Re: PolarAxes project |
Date: | Mon, 2 Mar 2020 08:16:22 -0800 |
On 03/02/2020 03:32 AM,
address@hidden wrote:
The m-file function will be polaraxes. This will perform input validation, have a help string, contain a few BIST tests. It should have compatible syntax with Matlab (https://www.mathworks.com/help/matlab/ref/polaraxes.html). The m-file will need to call C++ code to create an actual polaraxes object. In axes.m, the call is htmp = __go_axes__ (hpar, varargin{:}); The code for __go_axes__, and for __go_polaraxes__ when it is developed, is in libinterp/corefcn/graphics.cc.
These are quite different. axes.m creates an axes object, whereas axis.m modifies the properties of an existing object by, for example, changing the limits of the x-axis or changing the aspect ratio.
The function polar.m in scripts/plot/draw implements what appears to be polar axes using a regular 2-D axes object. The project should not be to replicate this in C++, but to create a brand new graphics object that is specifically for displaying polar axes.
This is looking for the property/value pair "parent"/figure_graphics_handle. If there is no such property given, Octave uses the current figure handle (gcf). --Rik |
[Prev in Thread] | Current Thread | [Next in Thread] |