Open Actor on PN NondeterministicMerge results in being prompted for Save

[cxbrooks]

Note: the issue was created automatically with bugzilla2github tool

Original bug ID: BZ#357 From: @cxbrooks Reported version: 8.1.devel CC: pt-dev@chess.eecs.berkeley.edu

[cxbrooks]

Edward wrote:

I suspect that someone (me?) did an "Open Actor" on the NondeterministicMerge in ActorA, which caused the _location parameter of the director and ports to be set, and did not do the same thing with ActorB. Once any parameter (including _location) is either added or modified, the entire hierarchy above it has to be included in the MoML file.

Edward

On 2/18/11 8:17 AM, Hauke Fuhrmann wrote:

Dear Ptolemy folks,

just a short question:

In the PN Domain BrockAckerman example, the NondeterministicMerge in "Actor A" has a

<property name="director" class="ptolemy.domains.pn.kernel.NondeterministicMerge$MergeDirector">

and some other contents like ports while in "Actor B" the NondeterministicMerge has not (see below). Why?

Cheers, Hauke

Actor A merge:

<entity name="NondeterministicMerge" class="ptolemy.domains.pn.kernel.NondeterministicMerge"> <property name="director" class="ptolemy.domains.pn.kernel.NondeterministicMerge$MergeDirector"> <property name="_location" class="ptolemy.kernel.util.Location" value="{0.0, 0.0}"> <property name="_location" class="ptolemy.kernel.util.Location" value="{210.0, 160.0}">

     <port name="output" class="ptolemy.actor.TypedIOPort">
         <property name="output"/>
         <property name="_location"

class="ptolemy.kernel.util.Location" value="{0.0, 0.0}">

 </entity>

---

Actor B merge:

<entity name="NondeterministicMerge" class="ptolemy.domains.pn.kernel.NondeterministicMerge"> <property name="_location" class="ptolemy.kernel.util.Location" value="{210.0, 160.0}">

[cxbrooks]

I took a look at the PN BrockAckerman demo and the two NondeterministicMerge actors do not have excess MoML.