search

cxbrooks / test

Second test for bugzilla to git
0 stars 0 forks source link

Creating Hierarchy: problems when relations directly linked to each other #130

Open cxbrooks opened 16 years ago

cxbrooks commented 16 years ago

Note: the issue was created automatically with bugzilla2github tool

Original bug ID: BZ#198 From: Bert Rodiers <bert.rodiers@gmail.com> Reported version: 7.1.devel CC: pt-dev@chess.eecs.berkeley.edu

cxbrooks commented 16 years ago

In a link is the border of a selection, the current code expects that on one side the link is connector with an actor-port. If this is not the case the link is removed and the newly created composite actor has no ports.

An example:

<?xml version="1.0" standalone="no"?> <!DOCTYPE entity PUBLIC "-//UC Berkeley//DTD MoML 1//EN" "http://ptolemy.eecs.berkeley.edu/xml/dtd/MoML_1.dtd">

Create a sequence of tokens with increasing value Create a sequence of tokens with increasing value

relation1 is linked with relation. If create a hierarchy with the border of your selection on the edge between both relations, you have a port in the composite actor and you hence also miss the link between both.

cxbrooks commented 16 years ago

(Hmm, I made some typing errors in the above description. I hope it is still clear)

Anyway, fixing this in general (so not for this example) with the current implementation is not that easy, except maybe if I would add an input/output port in the composite actor instead of trying to find our whether it should be an input or output port. Probably this hierarchy problem is also less important that than the already reported ones.