[kepler-dev] subclassing actors: ptolemy.actor.lib.MonitorValue

[Paul Allen]

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>
    <property name="displayWidth" class="ptolemy.data.expr.Parameter" 
value="displayWidth">
    </property>
</property>

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.
>
> -Paul
>
>
> _______________________________________________
> Kepler-dev mailing list
> Kepler-dev at ecoinformatics.org
> http://mercury.nceas.ucsb.edu/ecoinformatics/mailman/listinfo/kepler-dev
>