Problems updating images, NonBooleanReceiver: proceed for truth.

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Problems updating images, NonBooleanReceiver: proceed for truth.

Karl Ramberg
I suspect it's Morphic-mt.1163.mcz that give the error.


See attached debug log.

Best,
Karl

Off topic kind of:
(I called the directory for the image trump instead of trunk as a pun for my self. I did not know I was going to post this. Sorry )



SqueakDebug.log (22K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Problems updating images, NonBooleanReceiver: proceed for truth.

marcel.taeumel
Karl Ramberg wrote
I suspect it's Morphic-mt.1163.mcz that give the error.


See attached debug log.

Best,
Karl

Off topic kind of:
(I called the directory for the image trump instead of trunk as a pun for
my self. I did not know I was going to post this. Sorry )




SqueakDebug.log (22K) <http://forum.world.st/attachment/4899257/0/SqueakDebug.log>
Hi, Karl.

You can safely ignore that. It is just a hick-up because there were many changes in HandMorph and Morph event processing.

If you click the update entry in the menu, after the update, there is also code to execute left on the stack (old CompiledMethods) which is only partially valid after the update.

The safest way around this "update problem" is by triggering the update *not* with mouse or keyboard input, hence, via the command line.

Anyway, you can ignore that issue.

Best,
Marcel
Reply | Threaded
Open this post in threaded view
|

Re: Problems updating images, NonBooleanReceiver: proceed for truth.

marcel.taeumel
marcel.taeumel wrote
Karl Ramberg wrote
I suspect it's Morphic-mt.1163.mcz that give the error.


See attached debug log.

Best,
Karl

Off topic kind of:
(I called the directory for the image trump instead of trunk as a pun for
my self. I did not know I was going to post this. Sorry )




SqueakDebug.log (22K) <http://forum.world.st/attachment/4899257/0/SqueakDebug.log>
Hi, Karl.

You can safely ignore that. It is just a hick-up because there were many changes in HandMorph and Morph event processing.

If you click the update entry in the menu, after the update, there is also code to execute left on the stack (old CompiledMethods) which is only partially valid after the update.

The safest way around this "update problem" is by triggering the update *not* with mouse or keyboard input, hence, via the command line.

Anyway, you can ignore that issue.

Best,
Marcel
We could change UserInputEvent >> #wasIgnored to check for nil, since during this update process #initialize was not called on the existing instances. However, then it wouldn't be a quick-return anymore. Event handling is critical for performance.

I would rather leave it that way... Opinions?

Best,
Marcel