Path: csiph.com!newsfeed.hal-mli.net!feeder3.hal-mli.net!newsfeed.hal-mli.net!feeder1.hal-mli.net!npeer03.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nx02.iad01.newshosting.com!newshosting.com!198.186.194.249.MISMATCH!transit3.readnews.com!news-out.readnews.com!news-xxxfer.readnews.com!s09-11.readnews.com!unm2.readnews.com.POSTED!not-for-mail
X-Trace: DXC=[dfUIjA4ZW7gK4fE:CPG_:@lWf8?fSK:1jS@R6]oDiI?[j;g`C24>V;o=iH@LQ<Yb04o5\H=^m?D4;0QGg><XR8<RKPEReo9dn4\bFHbWGH9F4
X-Complaints-To: abuse@gradwell.net
Subject: An easy way to let the WIMP update?
Newsgroups: comp.sys.acorn.programmer
From: Gavin <gc@dentrassis.com>
X-Editor: EmailEdit 1.50
Date: Fri, 30 Mar 2012 14:36:36 +0100
Message-ID: <2cdb947852.Dentrassis@mail>
User-Agent: Messenger-Pro/5.13 (MsgServe/3.43) (RISC-OS/5.18) NewsHound/v1.52-32
Lines: 26
Organization: readnews.com - News for Geeks and ISPs
NNTP-Posting-Host: 290a6116.newsreader.readnews.com
X-Received-Bytes: 2070
Xref: csiph.com comp.sys.acorn.programmer:1549

Is there an easy way to let the WIMP and other tasks update their 
windows etc, in between my app doing some processing?

I have a simple application that processes a file when it dropped over 
it's icon. During the processing there is no multi-tasking going on as 
my simple BASIC program hogs the machine until it's finished, and I 
next call Wimp_Poll. That's fine, and I don't want to go to the effort 
of re-writing it to process in the background or use a taskwindow etc. 

But what I would like, if there is a simple way of doing it, is allow 
the WIMP and the Filer to update between each file being processed, 
when there is a selection of files all dragged in at the same time to 
my app. I wondered if calling Wimp_PollIdle after processing a file 
was the way to do it, to sort of force a null poll for other apps to 
receive, but my app is receiving a sequence of data load messages that 
have been queued up from the selection being dragged in, so I 
immediately start processing the next file.

I'm wondering if a better approach is to build a list of all the files 
to be processed when they are first dragged in, then work through that 
list (and only start the processing) on the next null poll I receive.

Any thoughts?

-- 
Gavin