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

[Jordi Gutiérrez Hermoso]

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

Ben,

I hope I'm not adding noise to an already very populated bug report, but here
is my analysis of your request: all of the __go_foo__ objects are essentially
the "same" object: a collection of name-value properties and a pointer to a
parent. They are all implemented the same way; the only thing that changes is
the name of the object. AIUI, you want the "string" property of __go_text__ to
accept cell strings in addition to ordinary strings, as well as character
arrays, for reasons I don't understand. I was stepping through the code, and I
think this should be easy to do, but then any other __go_foo__ object that has
a "string" property could also accept cell string values.

If this is what you want, I can prepare a patch quite easily. If only the
"string" property of __go_text__ should accept cell strings, that would
require more in-depth hackery.

Do you also want character arrays or just cell strings?

    _______________________________________________________

Reply to this item at:

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

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