Re: Issue 596 in moose-technology: Name of the project not set when importing from Smalltalk
Updates: Summary: Name of the project not set when importing from Smalltalk Labels: Component-Finder
Comment #2 on issue 596 by tudor.gi...@gmail.com: Name of the project not set when importing from Smalltalk http://code.google.com/p/moose-technology/issues/detail?id=596
I took a look and it seems to be related to TextMorph, or at least the way it is setup. If you accept the text, it the name is properly set.
I do not know how to setup the TextMorph not to require an accept. Cyrille?
Comment #3 on issue 596 by jannik.l...@gmail.com: Name of the project not set when importing from Smalltalk http://code.google.com/p/moose-technology/issues/detail?id=596
I do not know how to solve this. I tried to hardcode this, to see what happen:
in MooseImportFromSmalltalkImageWizard>>performTerminateButtonAction, I added this line to force accepting the text: (self wizardPanes second partsAndInformationsAssociated keyAtValue: #modelName) merlinRendering textField textMorph acceptContents.
But it keeps 'MooseModel'.
Cyrille any idea ? We should validate the content when the field lose the focus.
Comment #4 on issue 596 by cy.delau...@gmail.com: Name of the project not set when importing from Smalltalk http://code.google.com/p/moose-technology/issues/detail?id=596
oops I didn't see yet this issue. I will look at that
Comment #5 on issue 596 by cy.delau...@gmail.com: Name of the project not set when importing from Smalltalk http://code.google.com/p/moose-technology/issues/detail?id=596
This should be fixed with the last version of Merlin
Updates: Status: Fixed
Comment #6 on issue 596 by jannik.l...@gmail.com: Name of the project not set when importing from Smalltalk http://code.google.com/p/moose-technology/issues/detail?id=596
works fine now.
-
moose-technology＠googlecode.com