[kepler-dev] subclassing actors: ptolemy.actor.lib.MonitorValue
cxh at eecs.berkeley.edu
Fri Aug 15 10:30:07 PDT 2008
Our email crossed.
I agree that how the xml file determines the icon is subtle.
Chapter 5 of Volume 1 of the Ptolemy II Design doc does not cover it.
I'll see about updating this sometime - I don't have access to
Framemaker right now.
Paul Allen wrote:
> I've answered my own question: The cool GUI functionality comes from an
> property in the MOML file in the definition of the MonitorValue <entity>
> <property name="_icon" class="ptolemy.vergil.icon.UpdatedValueIcon">
> <property name="attributeName"
> class="ptolemy.kernel.util.StringAttribute" value="value">
> <property name="displayWidth" class="ptolemy.data.expr.Parameter"
> I'm wondering which documentaiton I ignored that would have told me this.
> Paul Allen wrote:
>> I'm trying to add some additional functionality to
>> ptolemy.actor.lib.MonitorValue. I created a subclass BAPMonitorValue
>> that does nothing but have the BAPMonitorValue(CompositeEntity
>> container, String name) constructor calling, super(container, name).
>> When I open Kepler and use Tools->Instantiate Component and add my
>> actor to the work area, my actor looks completely different from the
>> normal MonitorValue actor.
>> Here's the question: How does ptolemy.actor.lib.MonitorValue get its
>> look and GUI functionality (i.e., showing it's current value)? It's
>> not defined in the ptolemy.actor.lib.MonitorValue class (or super
>> classes) as far as I can tell.
>> Kepler-dev mailing list
>> Kepler-dev at ecoinformatics.org
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
Christopher Brooks (cxh at eecs berkeley edu) University of California
Chess Executive Director US Mail: 337 Cory Hall
Programmer/Analyst Chess/Ptolemy/Trust Berkeley, CA 94720-1774
ph: 510.643.9841 fax: 510.642.2718 (office: 400A Cory)
home: (F-Tu) 707.665.0131 (W-F) 510.655.5480
More information about the Kepler-dev