I apologize if this is known and worked on...
We really like the rework that has happened on the ptolemy.data and
ptolemy.data.expr packages, it seems it will be beneficial for us as well...
However, the following quite common pattern has now been broken. If you try
to open the composite example below, the process of cloning
.composite2.entity1.const.par will not get the scope and throws an
exception...
Regards and thanks,
Zoltan Kemenczy
Research in Motion Limited (www.rim.net)
305 Phillip St, Waterloo, Ontario Canada N2L 3W8
<?xml version="1.0" standalone="no"?>
<!DOCTYPE model PUBLIC "-//UC Berkeley//DTD MoML 1//EN"
"http://ptolemy.eecs.berkeley.edu/xml/dtd/MoML_1.dtd";>
<entity name="composite" class="ptolemy.actor.TypedCompositeActor">
<property name="internalOsr" class="ptolemy.data.expr.Parameter"
value="16">
</property>
<entity name="composite2" class="composite2">
<property name="par1" class="ptolemy.data.expr.Parameter" value="1">
</property>
</entity>
</entity>
<?xml version="1.0" standalone="no"?>
<!DOCTYPE class PUBLIC "-//UC Berkeley//DTD MoML 1//EN"
"http://ptolemy.eecs.berkeley.edu/xml/dtd/MoML_1.dtd";>
<class name="composite2" extends="ptolemy.actor.TypedCompositeActor">
<property name="par1" class="ptolemy.data.expr.Parameter" value="1"/>
<entity name="entity1" class="ptolemy.actor.TypedCompositeActor">
<property name="par" class="ptolemy.data.expr.Parameter" value="par1">
</property>
<entity name="const" class="ptolemy.actor.lib.Const">
<property name="value" value="par"
class="ptolemy.data.expr.Parameter"/>
</entity>
</entity>
</class>
----------------------------------------------------------------------------
Posted to the ptolemy-hackers mailing list. Please send administrative
mail for this list to: [EMAIL PROTECTED]
