Re: CompositeActor

2006-01-03 Thread Edward A. Lee
The problem is that the connection inside in the composite has width 1. If you double click on the connection and set the width to 2, then the behavior is the same for both models. If you set the width to 0, then the width will automatically be inferred to be 2 (or to be equal to however many co

CompositeActor

2006-01-03 Thread Andre
If I have a CompositeActor containing just an input port and a display sink and connect that to a DE domain model it gives other results than connecting the display directly. See attached moml for an example. Can someone tell me if this is intended and why. How can I avoid that? Thanks andre

Re: Evaluating String Parameters

2006-01-03 Thread Edward A. Lee
If you use Parameter in string mode, or use the StringParameter class (vs. StringAttribute), then you can give the value of a parameter as, for example: $numberOfIntegerBits.$numberOfFractionalBits numberOfIntegerBits and numberOfFractionalBits can be arbitrary parameters in scope. Edward

Re: Evaluating String Parameters

2006-01-03 Thread Michael J Wirthlin
I figured out my problem - sorry about the added mailing list noise (this took me quite a while to figure out). I now use a "Parameter" instead of a StringAttribute for the Precision parameter. Also, I found out that if I enclose the Precision string within quotes, (i.e. as "(1.8)"), the expr