From:	Paul Shirley <Paul AT no DOT spam DOT please>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: RHIDE: CPU working at full capacity
Date:	Thu, 15 Jan 1998 17:25:26 +0000
Organization:	wot? me?
Distribution:	world
Message-ID:	<RClOBSAGakv0EwTE@foobar.co.uk>
References:	<ccyt2zAef6u0Ewb1 AT foobar DOT co DOT uk>
	<Pine DOT SUN DOT 3 DOT 91 DOT 980114131057 DOT 8730D-100000 AT is>
Reply-To:	Paul Shirley <Paul AT chocolat DOT obvious DOT fake DOT foobar DOT co DOT uk>
NNTP-Posting-Host:	chocolat.foobar.co.uk
Mime-Version:	1.0
Lines:	31
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <Pine DOT SUN DOT 3 DOT 91 DOT 980114131057 DOT 8730D-100000 AT is>, Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> writes
>
>On Tue, 13 Jan 1998, Paul Shirley wrote:
>
>> Try setting the RHIDE dos box settings under Misc/Background to 'Always
>> suspend'. That should give the CPU back to windoze if you switch away
>> from RHide which may be enough. Alternatively its time to hack RHIDE.
>
>This might not be the right thing to do, if RHIDE uses the idle time
>to do something useful.  For example, Emacs will continue to syntax-
>highlight its buffers and to check whether buffers should be auto-
>saved when the keyboard is idle.  Telling Windows to "Always suspend"
>will cause RHIDE to not get any cycles when its window is not the
>active one, which will defeat such features (I don't know whether
>RHIDE uses them).

Stopping an editor doing syntax hilighting is not a valid reason to soak
up 90%+ of cpu time, especially since presumably you are looking at
whatever got the focus instead of RHide ;)

The big problem is that gcc will stop compiling if you make RHide a
background task. Since you can change the suspend status whilst running
its not quite a disaster (but annoying if you need to change it
regularly).

Ideally you fix fix the misbehaving app, the suspend option is just
another less effective (but easy) option.

---
Paul Shirley: my email address is 'obvious'ly anti-spammed

- Raw text -