[gme-users] Constraint definition errors

Zoltan Molnar zolmol at isis.vanderbilt.edu
Tue Feb 6 13:08:30 CST 2007

What does the File/Display Constaints menuitem say about those
constraints? Are they loaded and turned on or they are disabled?

Do those constraints use deprecated kindnames, which do not exist
anymore in the metamodel?


> -----Original Message-----
> From: gme-users-bounces at list.isis.vanderbilt.edu 
> [mailto:gme-users-bounces at list.isis.vanderbilt.edu] On Behalf 
> Of Sumant Tambe
> Sent: Tuesday, February 06, 2007 12:58 PM
> To: gme-users
> Subject: [gme-users] Constraint definition errors
> Hi folks,
> I am getting constraint definition errors to a bunch of constraints 
> while importing a model from an xme. But while editing the same 
> constraint in the Equation: box of a constraint, I don't get 
> any error. In other words, MetaGME does not scream at the 
> constraint but while 
> importing a model it does.
> This happens for the constraints that use 
> self.attachingConnections(*) 
> or self.ConnectedFCOs(*). The constraint definition error 
> says "Neither 
> Type, Variable, implicit attribute nor implicit Association 
> (*) exists." 
> Where in fact the association at the place of * does exist.
> These errors show up in CQML, which uses PICML as a library 
> and all the 
> types involved in the constraint are defined in CQML. Is it an issue 
> with namespaces?
> Please let me know if you have any clues.
> Thanks,
> Sumant.
> _______________________________________________
> gme-users mailing list
> gme-users at list.isis.vanderbilt.edu
> http://list.isis.vanderbilt.edu/mailman/listinfo/gme-users

More information about the gme-users mailing list