[Octave-bug-tracker] [bug #31468] multi-line text objects

[Ben Abbott]

Follow-up Comment #25, bug #31468 (project octave):

Jordi,

In text.m I see ...


 86         tmp = __go_text__ (ca, "string", label{1},
 87                            varargin{:},
 88                            "position", pos);


I think we want the "string" property value to be either character (rows x
length), or cell-strings.

Are you saying that all the __go_foo__ objects will need to be modified to
accept either cell, or character, inputs for "string" properties?

Currently, the ticklabels for axes objects and string properties for text
objects may be numeric, character, or cellstrings. Perhaps the same approach
can be used for "string" properties?

    _______________________________________________________

Reply to this item at:

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

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