=DEann 26-Sep-97 skrifar Arole Sundeepr:
>=20
> It would seem to make more sense to implement this feature manually, us=
ing
> perhaps two processes and some form of IPC. One process runs as the mai=
n
> program which handles the communication loop, and another process which
> manages the GUI (small window). When an event occurs the GUI process ca=
n=20
> interrupt the main program loop using IPC and a known protocol and pass=
along
> the necessary event information to the main loop.
>=20
It is a way to solve it, yes... but too messy IMO. And not to mention,
that we're using up a lot of unnecessary CPU time. If you had a few
programs like that running, let's say three, you'd have 6 processes of wh=
ich
three would be constantly polling the X interface, instead of only three
running until interrupted.
...or, like my old teach used to explain interrupts. If you're expecti=
ng
someone for dinner, and you're doing the cooking. Which makes more sense=
,
to be busy in the kitchen and run every minute to the door to see if your
guests are there? To hire a maid to do the cooking and sit by the peep ho=
le
until your guests arrive so you can see them arrive? ...or, do the cookin=
g
and open the door for your guests when the bell rings? :-)
-------------------------------------------------------------------------=
---
Orn Einar Hansen oe.hansen@oehansen.pp.se
oehansen@daimi.aau.dk
voice+fax; +46 035 217194
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/