Status: New Owner: ---- Labels: Type-Defect Priority-Medium
New issue 1027 by v.blonde...@gmail.com: The system doesn't open a warning window on #notify: http://code.google.com/p/moose-technology/issues/detail?id=1027
Describe the problem: what do you get? what do you expect?
When I try to send the message #notify: to an object, I get :
MessageNotUnderstood: receiver of "not" is nil.
In the method :
GTDebugger class>>openContext: aContext label: aString contents: contentsStringOrNil // <primitive: 19> "Simulation guard" ErrorRecursion not & // The class variable ErrorRecursion seems not initialized and should it be at 'false' like in Spec.
How to reproduce the problem: step by step if necessary
To reproduce, open a Workspace under Moose-5.0 and do : self notify: 'A Message'
It works under Pharo3.
Additional information: platform, context which may impact the problem
Linux x64, Moose-5.0 last version.
Please fill in the labels with the following information: * Type-Defect * Component-Debbugger
Comment #1 on issue 1027 by v.blonde...@gmail.com: The system doesn't open a warning window on #notify: http://code.google.com/p/moose-technology/issues/detail?id=1027
By adding the method :
GTDebugger class >> initialize super initialize. ErrorRecursion := false.
It seems to resolve a part of the problem. But the image is freezing instead.... And I don't know how to solve it.
Comment #2 on issue 1027 by chisvasi...@gmail.com: The system doesn't open a warning window on #notify: http://code.google.com/p/moose-technology/issues/detail?id=1027
Should be fixed in the latest version. The UI process was not handled correctly when using #notify:.
Comment #3 on issue 1027 by tu...@tudorgirba.com: The system doesn't open a warning window on #notify: http://code.google.com/p/moose-technology/issues/detail?id=1027
Andrei: Where was this problem handled?
Updates: Status: Fixed Labels: Component-GlamorousToolkit Milestone-5.0
Comment #4 on issue 1027 by tu...@tudorgirba.com: The system doesn't open a warning window on #notify: http://code.google.com/p/moose-technology/issues/detail?id=1027
Anyway, the problem is fixed now.