Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!mcsun!ukc!dcl-cs!dik
From: dik@comp.lancs.ac.uk (Mr R. M. Bentley)
Newsgroups: comp.lang.smalltalk
Subject: ScheduledWindows in r4
Message-ID: <1374@dcl-vitus.comp.lancs.ac.uk>
Date: 18 Jun 91 16:43:05 GMT
Reply-To: dik@dcl-cs.UUCP (Mr R. M. Bentley)
Organization: Department of Computing at Lancaster University, UK.
Lines: 32

I'm writing some code that requires Windows to be opened without
terminating the active process. ScheduledWindow provides a method
for this purpose - openIn:terminateActive:  I then go on to open
some more windows at points dependent on the position of the Window.
I'm getting problems in that sometimes the inputOrigin of the 
Window is not initialised properly, so Window returns the incorrect
origin in response to the message globalOrigin.

An example may help - 

  aWindow openIn: aRectangle terminateActive: false.
  Transcript show: aWindow globalOrigin printString.

Window changeCreationOrigin: aPoint is invoked twice during Window
initialisation. I sometimes pick up the value before the second 
invocation has set the correct globalOrigin. This should not be the
case if the activeProcess - the one running the code - is blocked
until the Process opening the Window has terminated (which I assumed
it was). I've tried forking the process that opens the Window at a
higher priority - (Processor activePriority + 1) - which has no  
effect.

Any comments welcome !

Richard Bentley

+------------------------------------+----------------------------+
| uucp :  ...!mcsun!ukc!dcl-cs!dik   |   Department of Computing  |
| arpa :  dik%lancs.comp@ucl.cs      |   University of Lancaster  |
| janet:  dik@uk.ac.lancs.comp       |   Bailrigg, Lancaster      |
| tel  :  (44) 524 65201 x3119       |   LA1 4YR,   UK.           |
+------------------------------------+----------------------------+