Re: [Pharo-project] building and installing a morph in the background

May 27, 2012

      On 27 May 2012 01:58, Tudor Girba <tudor@tudorgirba.com> wrote:
...
Hi,
I am trying to build a complex morph and install it in another morph in a background process such that it does not impact the rest of the user interface. After a discussion with Igor, I got to the code below (similar to what can be found in CodeAnnotationPane).
However, it still does not seem to have the desired effect as the main ui still appears to be blocked. Can anyone see any problem with the code?
The code can be found in the latest version of Glamour.
Cheers,
Doru
GLMWatcherWindow>>addContent: aBlockWhoseValueReturnsAMorph
Â  Â  Â  Â | newMorph |
Â  Â  Â  Â "if we are still rendering some contents for another watcher,
Â  Â  Â  Â we stop and replace with the current request"
Â  Â  Â  Â process ifNotNil: [ process terminate ].
Â  Â  Â  Â process := nil.
Â  Â  Â  Â process := [
Â  Â  Â  Â  Â  Â  Â  Â WorldState addDeferredUIMessage: Â [
Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â newMorph := aBlockWhoseValueReturnsAMorph value.
Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â self contentsMorph
Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â removeAllMorphs;
Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â  Â addMorph: newMorph fullFrame: (LayoutFrame fractions: (0@0 corner: 1@1))
Â  Â  Â  Â  Â  Â  Â  Â ]
Â  Â  Â  Â ] newProcess.
Â  Â  Â  Â process priority: Processor userBackgroundPriority.
Â  Â  Â  Â process resume
Sure thing, because you still building your morph in UI thread (inside
a block which you pass
to addDeferredUIMessage.

To make it clear,              WorldState addDeferredUIMessage:
can be rephrased as:

  WorldState evaluateThisBlockInUIProcess:

So, moving
 newMorph := aBlockWhoseValueReturnsAMorph value.
outside of this block will do the thing.
...
--
www.tudorgirba.com
"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."
-- 
Best regards,
Igor Stasenko.