[Top][All Lists]

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

unambiguous property match in graphics handle

From: John W. Eaton
Subject: unambiguous property match in graphics handle
Date: Tue, 9 Feb 2010 19:43:39 -0500

On  9-Feb-2010, E. Joshua Rigler wrote:

| Is it possible to force graphics handle functions like get/set to
| return/define unambiguous matches to incomplete property strings the
| same way ML does?  If not, has this been considered, and do any
| regular users or maintainers have an opinion on this functionality?
| For context, I am attempting to get the free ML mapping toolbox M_Map
| to work under Octave.  Most of the problems I have experienced so far
| relate to the fact that the author of this toolbox used abbreviated
| graphics property names like "ticklen" instead of "ticklength" (and
| many more).  I am currently working through the code and attempting to
| modify all such instances, but it would be nice if in the future
| something like M_map just worked without modification.

This feature is implemented in the current development sources, along
with a warning (that you can turn off with the
"Octave:abbreviated-property-match" warning ID) so that you will know
when you've abbreviated a property name and what the full name that
matches is.


reply via email to

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