Path: csiph.com!eternal-september.org!feeder.eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail From: Ronald Newsgroups: comp.sys.acorn.programmer Subject: Re: Calling Ghostscript from BASIC Date: Sun, 14 Jun 2020 20:27:36 +1200 Organization: - Lines: 29 Message-ID: <1cb5648058.beeb@-.-> References: <587d6e2a47rhnews@dsl.pipex.com> Injection-Info: reader02.eternal-september.org; posting-host="ad8997512acfc152b99603c18e8ebb32"; logging-data="27151"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/Wt5f1KPB/SEho04y/89Yq" User-Agent: Messenger-Pro/1.00c (MsgServe/1.00a) (RISC-OS/5.24) NewsHound/v1.50-32 Cancel-Lock: sha1:0Q5d6svVcptYa1pdYplIPNaYeN4= Xref: csiph.com comp.sys.acorn.programmer:6156 In message Steve Fryatt wrote: > On 14 Jun, Ronald wrote in message > : > > > I guess checking for a file or system variable to be set with some sort of > > wimp poll so it's not grinding away in a loop. I've been experimenting > > with pause%=INKEY 2000 any key press will stop the wait, useable to a > > degree. > > If you don't want to do the Message_TW_* stuff, then Message_TaskInitialise > and Message_TaskCloseDown, as I originally posted. That way, there's no > polling and no ugly time delay stuff: you just get messages sent in when > there's something new to test against. > So where is the waiting done, with Message_TaskCloseDown sitting there with the task handle (+4) you've asked for? Initially looks easy enough, the StrongHelp doesn't explain where you would get the information for Message_TaskInitialise +20 +24 +28 Not saying it wouldn't be worth the effort, it does sound like a job that a pre-existing library could do so you can just run what you want without delving into wimp offsets. The Zap complication hopefully will get fixed by Zap people. Ronald