octave-maintainers
[Top][All Lists]
Advanced

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

Re: terminology: handles, figures, objects, etc.


From: Michael D Godfrey
Subject: Re: terminology: handles, figures, objects, etc.
Date: Sat, 19 Sep 2009 18:56:33 -0700
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.1) Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Thunderbird/3.0b3

On 09/17/2009 05:20 PM, Michael D Godfrey wrote:
On 09/17/2009 03:16 PM, Robert T. Short wrote:
octave:1> f1 = figure(1);  %  This creates a figure object.  The handle is f1, but f1 is NOT an object.
octave:2> ishandle(f1)      %  You can see this by using ishandle and isobject.  The actual object is buried
ans =  1                            %   in the octave dataspace, and you can't get it directly but you CAN manipulate
octave:3> isobject(f1)       %  the properties through the handle.
ans = 0                             % Thus a handle is simple an opaque reference to the object.  It could be an index
=============================================
The above is true, but is not what the Manual says:

ishandle (h) [Built-in Function]
Return true if h is a graphics handle and false otherwise.
ishghandle (h) [Function File]
Return true if h is a graphics handle and false otherwise.
isfigure (h) [Function File]
Return true if h is a graphics handle that contains a figure object and false otherwise
=============================================
I believed the Manual when I wrote the earlier email.

So far the response suggests that a Section in the Manual devoted to the precise
definition of these terms would be a good idea.  I will circulate a draft soon.

Thanks,
Michael
Just noticed that this went only to Robert.
This is for the rest of the list.
Michael


reply via email to

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