Issue 655 in moose-technology: export a moose model raise an error

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

New issue 655 by [hidden email]: export a moose model raise an error
http://code.google.com/p/moose-technology/issues/detail?id=655

Try to import a smalltalk model in moose. Right click on the model  
and 'export to mse' . at the end of the export you will get:
      MessageNotUnderstood: receiver of "sender" is nil

I think it is related this issue :

   http://code.google.com/p/moose-technology/issues/detail?id=635

At the end of the export there is a notification signaling that the export  
succeed.
The new way announcements are dealing now with exception signals lead to  
those kind of behavior

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Labels: Component-Finder Component-MooseCore Milestone-4.6

Comment #1 on issue 655 by [hidden email]: export a moose model raise  
an error
http://code.google.com/p/moose-technology/issues/detail?id=655

The issue is that now if we write "Notification signal: 'Save successful!'"  
we get a debugger. Before we did not.

I do not know what is the preferred way to raise this notification now.  
Could you check?

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Comment #2 on issue 655 by [hidden email]: export a moose model  
raise an error
http://code.google.com/p/moose-technology/issues/detail?id=655

Yes that is the notification I was talking about. I by 'we get a debugger'  
i guess you mean that we have the error I described.
What I think is that the problem will come with any exception signaled  
during the process. Whatever the kind of Exception (here it's a  
notification).
So the easy is to not signal anything at the end

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Comment #3 on issue 655 by [hidden email]: export a moose model raise  
an error
http://code.google.com/p/moose-technology/issues/detail?id=655

This notification used to popup a modal dialog. We should not just directly  
open a model dialog because then you cannot deal with it. The nice thing  
about a notification is that it can be caught and dealt with  
programatically.

We do want to notify the user, but we should now see how this should be  
done in the new Pharo. Could you check? :)

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Cc: [hidden email]

Comment #4 on issue 655 by [hidden email]: export a moose model raise  
an error
http://code.google.com/p/moose-technology/issues/detail?id=655

Cyrille, could you provide a summary of the discussion from the Pharo  
mailing list on this issue?

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Comment #5 on issue 655 by [hidden email]: export a moose model raise  
an error
http://code.google.com/p/moose-technology/issues/detail?id=655

There is no error anymore. However, "Notification signal: 'xyz'" does not  
do anything anymore either.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev

Updates:
        Status: Fixed

Comment #6 on issue 655 by [hidden email]: export a moose model  
raise an error
http://code.google.com/p/moose-technology/issues/detail?id=655

We consider this one fixed.

_______________________________________________
Moose-dev mailing list
[hidden email]
https://www.iam.unibe.ch/mailman/listinfo/moose-dev