[gme-users] ports on a reference

[Brian Williams]

If you're adventurous, you could write a custom decorator for just the
reference, but if you have other ports that do need to show up, it would
be a pain.

Brian

-----Original Message-----
From: gme-users-bounces at list.isis.vanderbilt.edu
[mailto:gme-users-bounces at list.isis.vanderbilt.edu] On Behalf Of Brandon
Eames
Sent: Thursday, June 08, 2006 12:52 PM
To: gme-users
Subject: RE: [gme-users] ports on a reference

Thanks for the suggestion.  
It sounds like it would work, but the downside is that I would have an
extra aspect for model A, that, from a user's perspective, serves no
purpose.  I'm just curious if there is another way around this issue
without encumbering the model with an extra aspect.

Thanks.

> -----Original Message-----
> From: gme-users-bounces at list.isis.vanderbilt.edu [mailto:gme-users-
> bounces at list.isis.vanderbilt.edu] On Behalf Of Ace Thompson
> Sent: Thursday, June 08, 2006 11:46 AM
> To: 'A list for GME users to share thoughts and discuss bugs and
fixes.'
> Subject: RE: [gme-users] ports on a reference
> 
> 
> One thing you can do is to give your model "A" another aspect (call it
> "E"),
> but don't put the port objects in that aspect...  Then when you run
the
> meta-interpreter, it will give you a "Configure Aspect Mapping"
dialog;
> you'll want to find the tab for aspect "D" and for role "B:R" use
> KindAspect
> "E" instead of "C".
> 
> This should make it so that GME uses aspect "E" (which doesn't contain
the
> port objects) when it visualizes an "R" inside of a "B" model, i.e. no
> ports...
> 
> Good luck!
> 
> -ace
> 
> -----Original Message-----
> From: gme-users-bounces at list.isis.vanderbilt.edu
> [mailto:gme-users-bounces at list.isis.vanderbilt.edu] On Behalf Of
Brandon
> Eames
> Sent: Thursday, June 08, 2006 10:20 AM
> To: gme-users at list.isis.vanderbilt.edu
> Subject: [gme-users] ports on a reference
> 
> Hi All,
> 
> I thought I knew the answer to the following question, but practical
> experience dictates otherwise.
> 
> I have a model (A) which contains ports.  Model A is assigned aspect
C,
> as is the parent of model A.  The ports, as well as model A are
allowed
> to be visualized in aspect C.
> 
> I have a reference (R) to model A.  I have another model (B) which can
> contain R, but not A.  Model B is assigned aspect D (different from
> aspect C).  Reference R is allowed to be visualized in Aspect D.  R is
> not allowed to be visualized in aspect C.  The ports of A are not
> allowed to be visualized in Aspect D.
> 
> The question is when I drop a reference to a model of type A into a
> model of type B, why do I see the ports of the model to which the
> reference refers on the edge of the reference?  I thought that in
order
> for that to work the ports would have to be "roped into" aspect D in
the
> metamodel?
> 
> Is there a way around seeing the ports on the reference?
> 
> Thanks,
> Brandon.
> 
> --------------------------------------------
> Brandon Eames, PhD
> Assistant Professor
> Electrical & Computer Engineering
> Utah State University
> Phone: (435) 797-2841
> 
> 
> _______________________________________________
> gme-users mailing list
> gme-users at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/gme-users
> 
> 
> _______________________________________________
> gme-users mailing list
> gme-users at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/gme-users
_______________________________________________
gme-users mailing list
gme-users at list.isis.vanderbilt.edu
http://list.isis.vanderbilt.edu/mailman/listinfo/gme-users