[Top][All Lists]

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

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

From: Jordi Gutiérrez Hermoso
Subject: [Octave-bug-tracker] [bug #31468] multi-line text objects
Date: Sat, 13 Aug 2011 00:56:47 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20110109 Superdingo/3.6.13

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


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:


  Message sent via/by Savannah

reply via email to

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