Path: utzoo!mnetor!uunet!husc6!cmcl2!nrl-cmf!ames!pasteur!ucbvax!USU.BITNET!FATQW
From: FATQW@USU.BITNET
Newsgroups: comp.sys.amiga
Subject: Re: A proposal for DOS 1.4
Message-ID: <8801191807.AA13288@jade.berkeley.edu>
Date: 19 Jan 88 17:03:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 21

This sounds good.  However, I think, for the ChActivPri function, it should
use a RELATIVE priority.  When this window gets activated, that task's
priority stays the same, but in the scheduling part of Exec, it, instead of
simply sticking it in the list where its priority is, stick it in the list
using a priority of normal priority+active priority.  That way it won't
change the task's priority in any way, but you'd still have that nice feature
Also, since Intution and Exec are not *really* related, I think you should
have ChActivPri in Exec, but also, UseActivPri, also in Exec, which "activate"
a task, which adjusts its priority by the ActivPri for the task, and de-
adjusts the old active task.  When a window gets activated in Intuition, it
would call UseActivPri in Exec with a pointer to the task that opened the
window.

I hope this doesn't slow down task multiplexing too much...

                                       Bryan

       Bryan Ford                  ///// A computer does what \\\\\
Snail: 1790 East 1400 North       ///// you tell it to do, not \\\\\
       Logan, UT 84321        \\\XX///  what you want it to do. \\\XX///
Email: USU@FATQW.BITNET        \XXXX/ Murphy's Law Calender 1986 \XXXX/