Issue 1033 in moose-technology: The result of loading a model from an MSE file is an OrderedCollection, not a MooseModel

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 1033 by [hidden email]: The result of loading a model from an  
MSE file is an OrderedCollection, not a MooseModel
http://code.google.com/p/moose-technology/issues/detail?id=1033

When loading a model from an MSE file, the result is not a MooseModel per  
se, but an OrderedCollection of various types (methods, invocations,  
accesses), and probably everything that should be inside, except that it is  
unstructured.

Experienced this on a Windows platform, with the latest version of Moose  
(5.0 development on Pharo 3).


--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Status: Fixed
        Labels: Component-Glamour Milestone-5.0

Comment #1 on issue 1033 by [hidden email]: The result of loading a  
model from an MSE file is an OrderedCollection, not a MooseModel
http://code.google.com/p/moose-technology/issues/detail?id=1033

This was an error in a recent Glamour commit.

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev