Thread View: comp.sys.acorn.tech
1 messages
1 total messages
Started by MUFTI
Mon, 14 Dec 1992 08:31
piping darkness into the wimp
Author: MUFTI
Date: Mon, 14 Dec 1992 08:31
Date: Mon, 14 Dec 1992 08:31
26 lines
1329 bytes
1329 bytes
Hi
Is there a idea for the following problem:
I use program for a interpreter, which should do Wimppolling.
If the interpreter fails (cause no memory left or the like), it prints a
message to vdu:
I want to catch such a message (the wimp will not show it) and a commandwindow
will not survive the initialisation of the wimp)
If i try to catch the message with a pipe { > output } the desktop
goes dark (with a few icons) and the wimppoll will write into the file
and there is no multitasking
If i try to catch the message with spool, all actions in the wimp will
logged into the outputfile (which may increase to big) (This will also
take time (especially on a diskette based system))
In my opinion, we need a errorstream (something like { 2> })
so long
MUFTI
ps: I use Riscos 2.0, the interpreter is iconx
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads