From mint-bounce@lists.fishpool.fi Thu Jul 7 17:53:21 2005 X-Original-To: fnaumann@mail.boerde.de Delivered-To: fnaumann@mail.boerde.de Subject: Re: [MiNT] [XAAES] Does not generate MU_TIMER events when asked From: Odd Skancke To: MiNT List In-Reply-To: <20050707173558.6c03162d.mandin.patrice@wanadoo.fr> References: <20050707132928.155c2829.mandin.patrice@wanadoo.fr> <1120737364.5673.93.camel@linuxbox> <1120741253.5673.106.camel@linuxbox> <20050707161808.4ca22b12.mandin.patrice@wanadoo.fr> <1120749916.5673.132.camel@linuxbox> <20050707173558.6c03162d.mandin.patrice@wanadoo.fr> Content-Type: text/plain; charset=utf-8 Date: Thu, 07 Jul 2005 17:48:52 +0200 Message-Id: <1120751333.5673.140.camel@linuxbox> Mime-Version: 1.0 X-Mailer: Evolution 2.0.4 (2.0.4-4) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-To: mint-bounce@lists.fishpool.fi X-original-sender: ozk@atari.org Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: X-Virus-Scanned: by amavisd-new at relay.boerde.de X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on relay.boerde.de X-Spam-Status: No, hits=-0.8 tagged_above=-50.5 required=7.0 tests=AWL, BAYES_00 X-Spam-Level: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by wh58-508.st.uni-magdeburg.de id j67FrLvk014991 tor, 07,.07.2005 kl. 17.35 +0200, skrev Patrice Mandin: > Le Thu, 07 Jul 2005 17:25:16 +0200 > Odd Skancke a écrit: > > > > This is fixed on my side, I was using MU_M1 and MU_M2 at the same > > > time, preventing any MU_TIMER from triggering. > > > > Yes .. but now it is triggering because of the change... > > And this is what I was expecting: triggering MU_TIMER after a specified > delay timed out, which is its purpose. Well, yes, but this is not the truth. You tell evnt_multi() you want 10ms delay. If some other event happened before this timeout triggered, XaAES would reset the timeout to a full new 10ms. And you used M1/M2 in such a way that evnt_multi() always returned, either when mouse was in M1 or when in M2. So, the timer never triggered. Under 'other AES', the 10ms delay is not reset, so even when you tell evnt_multi() you wanted 10ms, you would get what remains of the FIRST MU_TIMER you set. So, if each evnt_multi() in this case took 1ms, you would get a MU_TIMER each 10th evnt_multi(), even tho this is not logical since you do tell it to wait 10ms. So what is the logical purpose of MU_TIMER? However, XaAES is now changed to the 'other AES' method for compatibility. Best Regards Odd Skancke