{5} Assigned, Active Tickets by Owner (Full Description) (7 matches)

List tickets assigned, group by ticket owner. This report demonstrates the use of full-row display.

kolczyk (1 match)

Ticket Summary Component Milestone Type Created
Description
#178 Drag&Drop: Visualizing of drop targets PromotGuiBase Promot 0.9 enhancement Aug 3, 2009

When dragging from a module in the ModulesPalette? of the Visual Editor to the tree in the browser the dragImage visualizes that a treenode is a drop target. Also drag&drop from PromotTreeNode? to PromotTreeNode?.

mirschel (4 matches)

Ticket Summary Component Milestone Type Created
Description
#133 Crash of the Java VM while using the ProMoT Explorer PromotGuiVizNav Promot 1.0+ defect Oct 17, 2008

The Java VM crashes while extensively using the zoom function of the ProMoT Explorer. This seems to be somehow related to the paint update routines of the explorer (especially during many successive updates). Probably this is a problem of the underlying libs like piccolo or graphics2d. Maybe it is related to limited memory. Reproducibility is not given. But it occurs often when extensively zooming in and out or zoom into some of the label glyphs.

#161 Extension of import format for attributes in explorer PromotGuiVizNav Promot 0.9 enhancement Mar 6, 2009

Present format see header of org.mpg.dcts.promot.viznav.data.io.AttributeReader.java

For future work we need a way to encode parts of hyper edges not only the whole hyperedge, e.g. TargetNode <tab> SourceNodeX <tab> SourceNodeY <specialtab> SourceNodeX <tab> !AttributeValue1 <tab> !AttributeValue2 <tab> AttributeValueN

The row above means we have attributes for the construct 'SourceNodeX (AND, OR) SourceNodeY results in TargetNode'. The second occurrence of SourceNodeX means that we want consider only the edge from SourceNodeX to TargetNode, thus only one part of the hyper edge. The edge from SourceNodeY to AND/OR will not be considered.

#111 Edit handle points of TerminalEdge PromotGuiVizEdit Promot 1.0 enhancement Jun 23, 2008

FigLinkEdge? can be modified by editing the bend (add or remove polyline handle point). This is helpful to layout the links in the network. FigTerminalEdge? do not have this facility but could be useful. The following steps are needed:

  • implement functionality (several methods are already implemented but seems to be not working correctly)
  • add options to the context menu of the edge
#237 Add option for import graphml with flat or simple names PromotGuiVizNav Promot 0.9 enhancement Oct 22, 2012

In the modeling cycle ProMoT-CNA-ProMoT sometimes layout information in the explorer are exported to graphml (using hierarchical names like moduleA.moduleB.componentC).

When the model is exported to CNA and thereafter reimported into ProMoT the model is represented as a 'flat' model. Hence the graphml information can not be applied anymore because the identifiers do not match (moduleA.moduleB.componentC vs. componentC).

So it would be nice to have an option in the graphml importer that provides also the handling for flat or simple names (used as identifers).

steinmet (2 matches)

Ticket Summary Component Milestone Type Created
Description
#109 extend checker for allowed terminal-types on a link in dynamical models. PromotGuiVizEdit Promot 0.9 enhancement May 20, 2008

a new checker case was added by [7660] for logical models. The modeler is alerted if he connects an input- and an output-terminal of one module by the same link. It would make sense to alert also if terminal-types in dynamical models are connected (e.g. conc_in and conc_out). It should be discussed with modelers, which combination of terminals would make sense.

#112 recalculation of LinkNode position after reloading a LinkProxy PromotGuiVizEdit Promot 1.0 defect Jun 24, 2008

fragment of former #24:

Some remarks of Martin

  • the `moving and jumping' happens for edge corners and LinkNodes?
  • The reason might be, that for reloading a LinkProxy? sometimes the algorithm detects bogus invalid edges.
  • The result of the effect above is, that it forgets about all the geometry information and generates a default `net' with the node placed into the gravity center of the connected terminals

A solution would be:

  • to be more precise with the invalid edges
  • to keep as much as possible information when invalidating a net (recalculate only the single edges that are invalid)
Note: See TracReports for help on using and creating reports.