Issue 869 in moose-technology: Smalltalk code presentation does not populate the text port
Status: New Owner: ---- CC: chisvasi...@gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7
New issue 869 by tu...@tudorgirba.com: Smalltalk code presentation does not populate the text port http://code.google.com/p/moose-technology/issues/detail?id=869
Typing in the code editor should populate the text port.
The test in GLMSmalltalkCodeMorphicTest>>testExplicitAcceptDoesNotAffectTextPort captures the problem.
See: http://ci.moosetechnology.org/job/moose-latest-dev/lastCompletedBuild/testRe...
Comment #1 on issue 869 by chisvasi...@gmail.com: Smalltalk code presentation does not populate the text port http://code.google.com/p/moose-technology/issues/detail?id=869
Adding a changedAction when building the morph seems to fix this problem (all tests are green): changedAction: [:aText| aText asString trimBoth ifNotEmpty: [aTextModel text: aText] ];
This should work because PluggableTextMorph>>textChanged triggers this action and is used in the case where we want to listen for live changes in a text morph, without triggering the accept behavior.
Comment #2 on issue 869 by tu...@tudorgirba.com: Smalltalk code presentation does not populate the text port http://code.google.com/p/moose-technology/issues/detail?id=869
Excellent. Funny that we missed this hook until now. This means that we can delete the autoAccept: true also from the regular text presentation. Could you look into that?
Comment #3 on issue 869 by chisvasi...@gmail.com: Smalltalk code presentation does not populate the text port http://code.google.com/p/moose-technology/issues/detail?id=869
Done. autoAccept: is no longer used with text presentations.
Updates: Status: Fixed
Comment #4 on issue 869 by tu...@tudorgirba.com: Smalltalk code presentation does not populate the text port http://code.google.com/p/moose-technology/issues/detail?id=869
Excellent.
-
moose-technology＠googlecode.com