Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!wuarchive!waikato.ac.nz!comp.vuw.ac.nz!jwright
Newsgroups: comp.sys.acorn
Subject: Re: Creation of a Taskwindow
Message-ID: <1991May07.053056.6557@comp.vuw.ac.nz>
From: Julian.Wright@comp.vuw.ac.nz (Julian Wright)
Date: Tue, 07 May 1991 05:30:56 GMT
Sender: news@comp.vuw.ac.nz (News Admin)
References: <1744@nlcvx.convex.nl> <6846@acorn.co.uk>
Distribution: comp
Organization: Not to speak of...
Nntp-Posting-Host: pencarrow.comp.vuw.ac.nz
Originator: jwright@pencarrow.comp.vuw.ac.nz
Lines: 27


I have superficially examined the TaskWindow module. It appears that,
unlike other *commands, the ShellCli_Task command this module provides
IS case sensative, and requires the syntax:

*ShellCLI_Task tttttttt wwwwwwww *command

where tttttttt is the task handle and wwwwwwww is the window handle of
the window to send output to and receive input from. The data is
transferred between the shellcli task and the window task via messages,
the format of which I have yet to decipher. The two handles are
specified in hex, with leading zeros to make them exactly 8 characters
in length each.

Could anyone at Acorn reading this (or anyone else for that matter)
please shed some light on the format of the messages? It would be very
nice to hit F12 and have a taskwindow pop up rather than have commands
scroll the desktop off the top of the screen... It might also be possible
to implement a 'virtual screen' via redirection to a sprite - and have
for example, the Basic Editor running in a window in the desktop...

    Cheers, Julian.
-- 
;`````````````````````````````````````````````````````````````````````````````;
; I would if I could but I can't so I won't but I might if I find I can later ;
;,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,;
jwright@comp.vuw.ac.nz                                julian@sideways.gen.ac.nz